From ronald.j.bynoe at intel.com Wed Nov 1 10:24:05 2017 From: ronald.j.bynoe at intel.com (Bynoe, Ronald J) Date: Wed, 1 Nov 2017 16:24:05 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 1! In-Reply-To: <59f34c9e3ccc9_21152932441022@boucane.mail> Message-ID: <1509553431.25352.19.camel@intel.com> We noticed that /etc/SuSE-release is missing from the Beta1 images. Was it omitted or has it been fully deprecated? If it has been deprecated, then anything depnding on CPython's platform.py is going to be broken, as it doesn't currently support os-release as far as I can tell. Pleasantly, Ronald Bynoe ND SW: IP Development QoS and Drivers Linux Validation Lead -------------- next part -------------- An HTML attachment was scrubbed... URL: From S.M.Flood at uis.cam.ac.uk Wed Nov 1 10:40:42 2017 From: S.M.Flood at uis.cam.ac.uk (Simon Flood) Date: Wed, 1 Nov 2017 16:40:42 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 1! In-Reply-To: <1509553431.25352.19.camel@intel.com> References: <1509553431.25352.19.camel@intel.com> Message-ID: On 01/11/17 16:24, Bynoe, Ronald J wrote: > We noticed that /etc/SuSE-release is missing from the Beta1 images. > > Was it omitted or has it been fully deprecated? If it has been deprecated, then anything depnding on CPython's platform.py is going to be broken, as it doesn't currently support os-release as far as I can tell. As noted in SLE12 SPx Release Notes: --begin-- Starting with SLE 12, the /etc/SuSE-release file has been deprecated. Do not use it to identify a SUSE Linux Enterprise system anymore. This file will be removed in a future Service Pack or release. To determine the release, use the file /etc/os-release instead. This file is a cross-distribution standard to identify Linux systems. For more information about the syntax, see the os-release man page (man os-release). ---end--- HTH, Simon -- Simon Flood HPC System Administrator University of Cambridge Information Services United Kingdom SUSE/Micro Focus Knowledge Partner From mmarion at qualcomm.com Wed Nov 1 12:02:05 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Wed, 1 Nov 2017 18:02:05 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 1! In-Reply-To: <1509553431.25352.19.camel@intel.com> References: <59f34c9e3ccc9_21152932441022@boucane.mail> <1509553431.25352.19.camel@intel.com> Message-ID: <20171101180204.GI28462@qualcomm.com> On Wed, Nov 01, 2017 at 04:24:05PM +0000, Bynoe, Ronald J wrote: > We noticed that /etc/SuSE-release is missing from the Beta1 images. > > Was it omitted or has it been fully deprecated? If it has been deprecated, then > anything depnding on CPython's platform.py is going to be broken, as it doesn't > currently support os-release as far as I can tell. Just ran into this yesterday as well, it's clear in the 12.3 file at least: == $ cat /etc/SuSE-release SUSE Linux Enterprise Server 12 (x86_64) VERSION = 12 PATCHLEVEL = 3 # This file is deprecated and will be removed in a future service pack or release. # Please check /etc/os-release for details about this release. == Already made mods to some of our scripts that had been looking at SuSE-release. Worried about the EDA software we support since those ISVs are slow to change. Back in the early days of us using sles we had to even spoof redhat-release files just to run many tools. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From adrian at suse.de Thu Nov 2 03:15:22 2017 From: adrian at suse.de (Adrian =?ISO-8859-1?Q?Schr=F6ter?=) Date: Thu, 02 Nov 2017 10:15:22 +0100 Subject: [sle-beta] first impressions, build service? In-Reply-To: References: Message-ID: <7332087.SMXg7Irghz@linux-izwb.site> On Dienstag, 31. Oktober 2017, 19:23:02 CET wrote Andreas Jaeger: > On 2017-10-31 19:20, Czanik, P?ter wrote: > > Hi, > > > > I just finished installing beta1 on a SoftIron Overdrive box (Aarch64) > > and I could not spot any extra bugs compared to x86! > > > > When can we expect build service support for SLES 15? I build all my rpm > > packages there and completely forgot how to build RPMs locally... :) I > > did a syslog-ng compile by hand, but using OBS would be a lot more > > convenient... > > The team has already started working on this and run into a few problems > with package set up that need fixing AFAIR, The setup is there already, you can configure your build against SUSE:SLE-15:GA / standard already. However, you will notice that some critical packages are missing, like "rpm-build". This is currently in the hand of the SDK release manager to fix it :) Your builds will start as soon as this got fixed ... -- Adrian Schroeter email: adrian at suse.de SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From S.M.Flood at uis.cam.ac.uk Thu Nov 2 05:00:51 2017 From: S.M.Flood at uis.cam.ac.uk (Simon Flood) Date: Thu, 2 Nov 2017 11:00:51 +0000 Subject: [sle-beta] SLES15 Beta 1 x86_64 observations In-Reply-To: <20171030154212.7aba3a23@pepa.labs.suse.cz> References: <20171030154212.7aba3a23@pepa.labs.suse.cz> Message-ID: On 30/10/17 14:42, Josef Reidinger wrote: > This is caused that installer is not yet adapted to new firewalld which > will replace SUSEFirewall2. It is known issue. > This is caused that installer is not yet adapted to new chrony which > will replace ntpd. It is also known issue. Thanks, makes sense. However the above, plus the replacement of openLDAP with 389-DS, prompts me to ask why the changes? I can see from https://chrony.tuxfamily.org/comparison.html why changing to chrony makes sense but what about firewalld and 389-DS? Given a certain other coloured Linux uses these applications it will be interesting to see what they make of it ... Thanks, Simon -- Simon Flood HPC System Administrator University of Cambridge Information Services United Kingdom SUSE/Micro Focus Knowledge Partner From kukuk at suse.de Thu Nov 2 06:14:54 2017 From: kukuk at suse.de (Thorsten Kukuk) Date: Thu, 2 Nov 2017 13:14:54 +0100 Subject: [sle-beta] SLES15 Beta 1 x86_64 observations In-Reply-To: References: <20171030154212.7aba3a23@pepa.labs.suse.cz> Message-ID: <20171102121454.GA15247@suse.de> On Thu, Nov 02, Simon Flood wrote: > Thanks, makes sense. However the above, plus the replacement of openLDAP > with 389-DS, prompts me to ask why the changes? > > I can see from https://chrony.tuxfamily.org/comparison.html why changing to > chrony makes sense but what about firewalld and 389-DS? 389-DS has more features and there are more and more tools requiring 389-DS and not working with openldap. firewalld: sometimes you have to throw away very old code and replace it with something newer, more maintainable. And SuSEfirewall2 is pretty old and has design limitations hurting a lot today, which are not fixable without a complete re-design. The world is continuing changing. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From vmoutoussamy at suse.com Thu Nov 2 07:22:44 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 2 Nov 2017 14:22:44 +0100 Subject: [sle-beta] xinetd In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D010E928703@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D010E928703@daeexmbx1.eur.ad.sag> Message-ID: <6B4EF3A6-2128-4D83-8776-5B5060502D2F@suse.com> Hi Dick, Antoine and Fr?d?ric gave you the information on why ?xinetd? was removed from SLES 15, but we need to track down the issue you reported with Yast2 Network Services. So could you please create a bug report with the component ?YaST2? and attach your YaST2 log files? Then post the bug number in this thread for reference. Thanks a lot. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 30 Oct 2017, at 18:30, Waite, Dick (External) wrote: > > Grand Evening, > > I'm having issues with "xinetd", it seems to be missing or lost ? > > Yast2 Network Services tells me it should be installed, so one tries and Yast2 says install of package failed.. > > __R > > Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From comet.friend at gmx.net Sat Nov 4 19:03:32 2017 From: comet.friend at gmx.net (Comet Friend) Date: Sun, 5 Nov 2017 02:03:32 +0100 Subject: [sle-beta] Again no KDE? Message-ID: <96f37d82-fd9c-bba3-5a63-7c31155799b9@gmx.net> Hi everyone, I know this has been discussed for SLE 12 in the past: Why is there no KDE included with SLE? Are there *any* technical or other facts based arguments? Forgive me the following rant --- I am big fan of KDE, and I'd *love* to see Plasma 5 running on Wayland in SLE by default. In the old thread the unproven claim was made that Gnome was "the industry standard" for desktop environments. Well, with 90% market share of Microsoft Windows, why don't you support that, then? The claim was obviously nonsense, and provoked some harsh replies. Dropping KDE was a bad mistake, IMHO. It has been the "native" desktop (with all the freedom of choice to use something else) of SUSE in the past and is beautifully running on openSUSE. The second argument for dropping KDE with SLE 12 was the reduced effort for support and maintenance. Well, this is again, half of an argument, and half untrue, because: (1) SUSE is one of the largest sponsors of the KDE project and actively contributing to this DE (and your developers are doing a great job, there!) So you continue to maintain KDE. Which is good! (2) Regarding the maintenance of the distribution (here: SLE), I wonder, why you are investing such an awful lot of work in Gnome to make it a SUSE desktop. You could easily drop this unnecessary effort and distribute upstream Gnome, instead. If Gnome really is "the industry standard", this would be the logical thing to do. So, while it is ok, that you want to focus on supporting only one desktop in corporate environments, the question is still un-answered: Why Gnome, and not KDE, when even the main competitor is supporting it? gargamel From malcolmlewis at cableone.net Sat Nov 4 20:26:46 2017 From: malcolmlewis at cableone.net (Malcolm) Date: Sat, 4 Nov 2017 21:26:46 -0500 Subject: [sle-beta] Again no KDE? In-Reply-To: <96f37d82-fd9c-bba3-5a63-7c31155799b9@gmx.net> References: <96f37d82-fd9c-bba3-5a63-7c31155799b9@gmx.net> Message-ID: <20171104212646.4c872b10@grover.homelinux.org> On Sun, 5 Nov 2017 02:03:32 +0100 Comet Friend wrote: > Hi everyone, > > I know this has been discussed for SLE 12 in the past: Why is there no > KDE included with SLE? Are there *any* technical or other facts based > arguments? > Hi Like SLE 12 SP2/SP3 I imagine it will be available via PackageHub.... https://packagehub.suse.com/ https://packagehub.suse.com/packages/patterns-sle-plasma5/ -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.90-18.32-default HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 up 23:39, 1 user, load average: 5.36, 2.35, 1.24 From talat.mellanox at gmail.com Sun Nov 5 02:18:17 2017 From: talat.mellanox at gmail.com (Talat mellanox) Date: Sun, 5 Nov 2017 11:18:17 +0200 Subject: [sle-beta] missing packages Message-ID: Hi everyone, We can't find the following packages in first beta of SLES-15-Server 1. perftest package 2. libibverbs-dev in order to install perftest package. 3. rpm-build package 4. libvma package 5. libreswan package 6. strongswan package 7. linuxptp package 8. UCX package 9. libpcre2-8.so.0 package. Git package doesn?t work properly. libpcre2-8.so.0: cannot open shared object file: No such file or directory could you please assist ? Yours, Talat -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Sun Nov 5 06:10:40 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Sun, 5 Nov 2017 13:10:40 +0000 Subject: [sle-beta] Again no KDE? In-Reply-To: <96f37d82-fd9c-bba3-5a63-7c31155799b9@gmx.net> References: <96f37d82-fd9c-bba3-5a63-7c31155799b9@gmx.net> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010E92AC1C@daeexmbx1.eur.ad.sag> Grand Sunday Afternoon, Your words are good and true, but I think there is more under the water than technical arguments. My friends and I tried very hard to have KDE as part of SLES/ SLED but it's like walking into the wind, or something similar. So join the good people using openSUSE LEAP 42. It's very close to SUSE-12 and has a very good KDE environment. From a development point of view it works well, but if you want to run production then you have to turn Red. I hope one day SUSE will come to understand that KDE is a good offering and it's what a lot of their customers want, but at the moment the tide is out, but like the tides it will change. __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Comet Friend [comet.friend at gmx.net] Sent: 05 November 2017 02:03 To: sle-beta at lists.suse.com Subject: [sle-beta] Again no KDE? Hi everyone, I know this has been discussed for SLE 12 in the past: Why is there no KDE included with SLE? Are there *any* technical or other facts based arguments? Forgive me the following rant --- I am big fan of KDE, and I'd *love* to see Plasma 5 running on Wayland in SLE by default. In the old thread the unproven claim was made that Gnome was "the industry standard" for desktop environments. Well, with 90% market share of Microsoft Windows, why don't you support that, then? The claim was obviously nonsense, and provoked some harsh replies. Dropping KDE was a bad mistake, IMHO. It has been the "native" desktop (with all the freedom of choice to use something else) of SUSE in the past and is beautifully running on openSUSE. The second argument for dropping KDE with SLE 12 was the reduced effort for support and maintenance. Well, this is again, half of an argument, and half untrue, because: (1) SUSE is one of the largest sponsors of the KDE project and actively contributing to this DE (and your developers are doing a great job, there!) So you continue to maintain KDE. Which is good! (2) Regarding the maintenance of the distribution (here: SLE), I wonder, why you are investing such an awful lot of work in Gnome to make it a SUSE desktop. You could easily drop this unnecessary effort and distribute upstream Gnome, instead. If Gnome really is "the industry standard", this would be the logical thing to do. So, while it is ok, that you want to focus on supporting only one desktop in corporate environments, the question is still un-answered: Why Gnome, and not KDE, when even the main competitor is supporting it? gargamel _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From jrd at netlab1.net Sun Nov 5 08:26:00 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Sun, 5 Nov 2017 15:26:00 +0000 Subject: [sle-beta] Network missing pieces Message-ID: <12b25390-6d4d-1df6-35a7-cca9cfe578c8@netlab1.net> ??? Perhaps this has been discussed previously and I missed it, but I found two major network components are missing: commands to support ifconfig and netstat. I have utilities which depend upon them, plus humans and their habits. ??? Further, we seem to be repeating the mistake of naming Ethernet interfaces in weird style, a matter which we thrashed out in SLES 12 some time ago. That means I expect to see eth0, eth1, rather than whimsical creations. ??? Thanks, ??? Joe D. From rbrown at suse.de Sun Nov 5 13:47:13 2017 From: rbrown at suse.de (Richard Brown) Date: Sun, 05 Nov 2017 21:47:13 +0100 Subject: [sle-beta] Network missing pieces In-Reply-To: <12b25390-6d4d-1df6-35a7-cca9cfe578c8@netlab1.net> References: <12b25390-6d4d-1df6-35a7-cca9cfe578c8@netlab1.net> Message-ID: On 2017-11-05 16:26, Joe Doupnik wrote: > ??? Perhaps this has been discussed previously and I missed it, but I > found two major network components are missing: commands to support > ifconfig and netstat. I have utilities which depend upon them, plus > humans and their habits. Hi Joe! Those tools (along with arp and route) have long been deprecated and should be substituted with their modern equivalents from the iproute2 package * arp -> ip [-r] neigh * ifconfig -> ip a * netstat -> ss [-r] * route -> ip r If you really, really, really want to continue to use the old unsupported tools I think SLE 15 has the 'net-tools-deprecated' package which will install them, but the package description gives the same recommendation as above. > Further, we seem to be repeating the mistake of naming Ethernet > interfaces in weird style, a matter which we thrashed out in SLES 12 > some time ago. That means I expect to see eth0, eth1, rather than > whimsical creations. The new interface naming is not 'whimsical' but solves real problems. I for one quite like the fact that I now have stable device naming regardless of tinkering with VM configurations, adding/removing cards on real hardware, etc etc A simple 'lspci' is all I need now to predictively create configuration required for a card, whereas with the previous model I could never be 100% certain my scripted 'eth0' configurations would land on the CORRECT card on the system. It's compatibility with a read-only root filesystem is also a boon for the work we're doing with CaaSP and Kubic. I'm quite sick of the bugs I have in Kubic right now because we haven't yet implemented this there as effectively as you see in the SLE-15 beta. There's a lot more information about this on the Freedesktop.org site: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Hope this helps, -- Richard Brown Linux Distribution Engineer - Future Technology Team Chairman - openSUSE Phone +4991174053-361 SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Felix Imend?rffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg) From jbohac at suse.cz Sun Nov 5 14:14:05 2017 From: jbohac at suse.cz (Jiri Bohac) Date: Sun, 5 Nov 2017 22:14:05 +0100 Subject: [sle-beta] Network missing pieces In-Reply-To: <12b25390-6d4d-1df6-35a7-cca9cfe578c8@netlab1.net> References: <12b25390-6d4d-1df6-35a7-cca9cfe578c8@netlab1.net> Message-ID: <20171105211405.4nhruedcfj5utrob@dwarf.suse.cz> Hi, On Sun, Nov 05, 2017 at 03:26:00PM +0000, Joe Doupnik wrote: > ??? Further, we seem to be repeating the mistake of naming Ethernet > interfaces in weird style, a matter which we thrashed out in SLES 12 some > time ago. That means I expect to see eth0, eth1, rather than whimsical > creations. this will be fixed. Tracked in bsc#1061883 (internal only). Submitrequest #145299, not sure if it's getting into the upcoming Beta3. Hope this helps, -- Jiri Bohac SUSE Labs, Prague, Czechia From talatb at mellanox.com Sun Nov 5 01:55:33 2017 From: talatb at mellanox.com (Talat mellanox) Date: Sun, 5 Nov 2017 09:55:33 +0200 Subject: [sle-beta] missing packages Message-ID: Hi everyone, We can't find the following packages in first beta of SLES-15-Server 1. perftest package 2. libibverbs-dev in order to install perftest package. 3. rpm-build package 4. libvma package 5. libreswan package 6. strongswan package 7. linuxptp package 8. UCX package 9. libpcre2-8.so.0 package. Git package doesn?t work properly. libpcre2-8.so.0: cannot open shared object file: No such file or directory could you please assist ? Yours, Talat -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrd at netlab1.net Mon Nov 6 04:48:07 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Mon, 6 Nov 2017 11:48:07 +0000 Subject: [sle-beta] Network missing pieces In-Reply-To: <260ba7aa-9ff5-927c-8b03-0ebad52e3ce4@netlab1.net> References: <260ba7aa-9ff5-927c-8b03-0ebad52e3ce4@netlab1.net> Message-ID: ??? Forwarding a copy to the beta list: ??? Without meaning to start a long discussion, I have the distinct feeling here that we have another classical "could versus should" situation. ??? In my view, the customer/end-user/human experience has high precedence about many matters of this kind. Thus classical tools ought to remain until there are clearly superior versions together marked need for those superior versions. If no such need then the classical ought to remain intact because the goal is to provide the end user with easy to use and remember controls, rather than play with the toys just because one could. There is also the unnecessary complexity part of things where replacement commands for standard straight forward operations require obtuse replacements and extra bits. Example: to open the house front door please hold the key upright in the mail slot while pointing one's left hand at the door's top hinge, which demonstrates our new nifty electro-optical lock mechanism (void during hurricane season). ??? The aspects of need and complexity become evident when dealing with more than one particular edition of Linux and with our sundry scripts and helpful programs which depend upon such features. Consider these aspects under stressful conditions involving many sundry Linux machines and there is some kind of trouble which must be fixed immediately by a duty manager. Consider what new customers would expect to be available [cf. the Windows 10 start menu fiasco]. ??? lspci. Gosh, I wonder how many people would think of that when dealing with a regular Ethernet adapter, even assuming the adapter were PCI based. Actually it does not help us, as readers can verify for themselves. Obscure ("whimsical") naming does no good either.? ethN (N = 0, 1..) is at least regular, predictable, some might say sensible and human oriented. Contrast that with "ens32" which can be followed next by say "ens34" (what happened to 33 or 31? Did I make an error somewhere?) which seem to have no obvious relationship to the observable world. The adapter name can be rectified manually, say via YaST or much more obscure tricks, but then arguably the regular system could/should have done that in the first place. ??? The freedesktop.org article (aka systemd again) is useful to read, so thanks for its reference in this discussion. In a nutshell or two it says they don't know what to do about an ideal AI solution (they haven't second guessed the kernel first guesser), so instead of solving that at the post boot level awkward special user commands are needed to restore rationality for even 90+% of situations. Think: a deer in headlights. Two quotations from the article: > Does this have any drawbacks? Yes, it does. Previously it was > practically guaranteed that hosts equipped with a single ethernet card > only had a single "eth0" interface. With this new scheme in place, an > administrator now has to check first what the local interface name is > before he can invoke commands on it where previously he had a good > chance that "eth0" was the right name. > That's documented in detail in a comment block the sources of the > net_id built-in > . > Please refer to this in case you are wondering how to decode the new > interface names. ??? Container projects seem to be inventing their own problems, and one hopes that over time those awkwardnesses would filter down into supporting kernel changes. An analogy is asking how many children's swings and houses a normal tree could support without requiring a new species. ?? Thus far in the discussed material I perceive neither superiority nor marked need, but I do see added complexity and obscurity.? I think the primary goal of usability by regular people is being lost in technical noise. Retaining tried and true tools while improving their underpinnings can be a satisfying achievement and be widely accepted. ??? Thanks, ??? Joe D. On 05/11/2017 20:47, Richard Brown wrote: > On 2017-11-05 16:26, Joe Doupnik wrote: >> ??? Perhaps this has been discussed previously and I missed it, but I >> found two major network components are missing: commands to support >> ifconfig and netstat. I have utilities which depend upon them, plus >> humans and their habits. > > Hi Joe! > > Those tools (along with arp and route) have long been deprecated and > should be substituted with their modern equivalents from the iproute2 > package > > ????? * arp -> ip [-r] neigh > ????? * ifconfig -> ip a > ????? * netstat -> ss [-r] > ????? * route -> ip r > > If you really, really, really want to continue to use the old > unsupported tools I think SLE 15 has the 'net-tools-deprecated' > package which will install them, but the package description gives the > same recommendation as above. > >> ??? Further, we seem to be repeating the mistake of naming Ethernet >> interfaces in weird style, a matter which we thrashed out in SLES 12 >> some time ago. That means I expect to see eth0, eth1, rather than >> whimsical creations. > > The new interface naming is not 'whimsical' but solves real problems. > I for one quite like the fact that I now have stable device naming > regardless of tinkering with VM configurations, adding/removing cards > on real hardware, etc etc > > A simple 'lspci' is all I need now to predictively create > configuration required for a card, whereas with the previous model I > could never be 100% certain my scripted 'eth0' configurations would > land on the CORRECT card on the system. > > It's compatibility with a read-only root filesystem is also a boon for > the work we're doing with CaaSP and Kubic. I'm quite sick of the bugs > I have in Kubic right now because we haven't yet implemented this > there as effectively as you see in the SLE-15 beta. > > There's a lot more information about this on the Freedesktop.org site: > > > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ > > > Hope this helps, -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbrown at suse.de Mon Nov 6 06:39:00 2017 From: rbrown at suse.de (Richard Brown) Date: Mon, 06 Nov 2017 14:39:00 +0100 Subject: [sle-beta] Network missing pieces In-Reply-To: References: <260ba7aa-9ff5-927c-8b03-0ebad52e3ce4@netlab1.net> Message-ID: <1509975540.28356.23.camel@suse.de> On Mon, 2017-11-06 at 11:48 +0000, Joe Doupnik wrote: > Without meaning to start a long discussion, I have the distinct feeling here that we have another classical "could versus should" situation. > In my view, the customer/end-user/human experience has high precedence about many matters of this kind. Thus classical tools ought to remain until there are clearly superior versions together marked need for those superior versions. If no such need then the classical ought to remain intact because the goal is to provide the end user with easy to use and remember controls, rather than play with the toys just because one could. There is also the unnecessary complexity part of things where replacement commands for standard straight forward operations require obtuse replacements and extra bits. Example: to open the house front door please hold the key upright in the mail slot while pointing one's left hand at the door's top hinge, which demonstrates our new nifty electro-optical lock mechanism (void during hurricane season). > The aspects of need and complexity become evident when dealing with more than one particular edition of Linux and with our sundry scripts and helpful programs which depend upon such features. Consider these aspects under stressful conditions involving many sundry Linux machines and there is some kind of trouble which must be fixed immediately by a duty manager. Consider what new customers would expect to be available [cf. the Windows 10 start menu fiasco]. "could" we install a package, by default, on all of our customers machines, which are intended to be supported for 10+ years, when the upstream of said package has been abandoned for over 8 years? Especially when the old tooling doesn't use many modern kernel features, many of which are required for fully supported SLE features like infiniband? And when the new tooling is both actively maintained and has been the designated successor for net-tools for 7 years, and developed for over 10. Sure, we "could", but the question then becomes "should" we? And I think it's the height of reasonableness to not inject a poster child example of legacy software on every SLE-15 machine by default. Like I said, it is still around as 'net-tools-deprecated' for those users who have no other choice, but a major new SLE version is exactly when we "could" and "should" make the necessary changes to distance ourselves from long abandoned tooling that no longer interacts with key components, like the kernel, in the correct way. -- Richard Brown Linux Distribution Engineer - Future Technology Team Chairman - openSUSE Phone +4991174053-361 SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From jrd at netlab1.net Mon Nov 6 08:13:18 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Mon, 6 Nov 2017 15:13:18 +0000 Subject: [sle-beta] Network missing pieces In-Reply-To: <1509975540.28356.23.camel@suse.de> References: <260ba7aa-9ff5-927c-8b03-0ebad52e3ce4@netlab1.net> <1509975540.28356.23.camel@suse.de> Message-ID: <316df77a-bbab-71de-c435-4baa584d6b90@netlab1.net> On 06/11/2017 13:39, Richard Brown wrote: > On Mon, 2017-11-06 at 11:48 +0000, Joe Doupnik wrote: >> Without meaning to start a long discussion, I have the distinct feeling here that we have another classical "could versus should" situation. >> In my view, the customer/end-user/human experience has high precedence about many matters of this kind. Thus classical tools ought to remain until there are clearly superior versions together marked need for those superior versions. If no such need then the classical ought to remain intact because the goal is to provide the end user with easy to use and remember controls, rather than play with the toys just because one could. There is also the unnecessary complexity part of things where replacement commands for standard straight forward operations require obtuse replacements and extra bits. Example: to open the house front door please hold the key upright in the mail slot while pointing one's left hand at the door's top hinge, which demonstrates our new nifty electro-optical lock mechanism (void during hurricane season). >> The aspects of need and complexity become evident when dealing with more than one particular edition of Linux and with our sundry scripts and helpful programs which depend upon such features. Consider these aspects under stressful conditions involving many sundry Linux machines and there is some kind of trouble which must be fixed immediately by a duty manager. Consider what new customers would expect to be available [cf. the Windows 10 start menu fiasco]. ??? That is a fair question, to which most of us would say if actual (vs just someone's perception) usefulness has nearly vanished while a better replacement is on offer then please do move us along, provided the consequences are manageable. ??? Again, the people and their applications parts of this equation are of high importance. Thus taking ifconfig as a handy example, removing its real code can/ought to result in a replacement which still fits people and systems, and that could be as simple as a shell alias. What we have gracefully left behind is supporting IP over carrier pigeons, token ring, and some other transports. ??? Exceptions to the rule dept. Clearly, Linux is not so simple as to have one utility fit every possible situation. We understand that. Where consideration is needed is evaluating the consequences of abandonment for the sake of a special case or a few narrow cases, versus keeping what exists and creating a tool to handle special cases. This evaluation is not purely about machinery. Yes, I am well aware of role playing here, where a Linux vendor might be drawn into rewriting some material just to keep it going (which they might do so if it serves a good business case, such as retaining customers). ??? It seems to me, thus just my perception, many authors while meaning well do get caught up in technique, stop short of completing solutions, and tend to forget larger consequences. We see this a lot, particularly with small projects. Whether or not a tool uses the latest in say processor features or similar is of much less importance than the tool itself continuing to work. Clearly, the reason is people and things created by/for them know and use the tool over the long term. As all of us appreciate, version/feature chasing is not friendly for production level work, yet it might cope with some newly arising important cases. Example: chasing versions of openssl to fend off the bad guys, but often encountering objections from some applications about mismatches (thus nearly rock & a hard place for awhile). ??? Poking about here for the "net-tools-depreciated" item. I don't see it in in SLE-15. So I dug deeper, enabled just about everything non-debug, no show. Next I followed that with enabling all search sources in YaST, and only then did it appear. I installed it, and ifconfig/netstat/et al now function. Whew! The point is they seem to work; the gibberish alternatives remain in the unnecessary gibberish category at this time. A bridge over troubled waters (unquote) has been provided. ??? Thanks, ??? Joe D. > "could" we install a package, by default, on all of our customers machines, which are intended to be supported > for 10+ years, when the upstream of said package has been abandoned for over 8 years? > Especially when the old tooling doesn't use many modern kernel features, many of which are required for fully > supported SLE features like infiniband? > And when the new tooling is both actively maintained and has been the designated successor for net-tools for 7 > years, and developed for over 10. > > Sure, we "could", but the question then becomes "should" we? > > And I think it's the height of reasonableness to not inject a poster child example of legacy software on every > SLE-15 machine by default. > Like I said, it is still around as 'net-tools-deprecated' for those users who have no other choice, but a > major new SLE version is exactly when we "could" and "should" make the necessary changes to distance ourselves > from long abandoned tooling that no longer interacts with key components, like the kernel, in the correct way. > > From kukuk at suse.de Mon Nov 6 09:28:59 2017 From: kukuk at suse.de (Thorsten Kukuk) Date: Mon, 6 Nov 2017 17:28:59 +0100 Subject: [sle-beta] SLES15 missing atftp? In-Reply-To: References: Message-ID: <20171106162859.GA22750@suse.de> On Mon, Nov 06, Sherry Crandall wrote: > We can't find atftp. Has it been removed from SLES15? Yes, we only ship tftp itself. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From mmarion at qualcomm.com Mon Nov 6 11:21:32 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Mon, 6 Nov 2017 18:21:32 +0000 Subject: [sle-beta] [resend] missing packages In-Reply-To: References: Message-ID: <20171106182131.GR7333@qualcomm.com> On Mon, Nov 06, 2017 at 04:53:59PM +0000, Joe Doupnik wrote: > Both UCX and libpcre2.8 are shown in YaST. The rest are not at my end. As > this is early in the beta program the missing may be on the to-do list. libpcre2.8 is in Desktop-Applications. I just ran into this myself. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From talatb at mellanox.com Mon Nov 6 11:36:38 2017 From: talatb at mellanox.com (Talat Batheesh) Date: Mon, 6 Nov 2017 18:36:38 +0000 Subject: [sle-beta] [resend] missing packages In-Reply-To: <20171106182131.GR7333@qualcomm.com> References: <20171106182131.GR7333@qualcomm.com> Message-ID: I'm using the Server distribution and I can't find it :~# zypper search libpcre2.8 Refreshing service 'SUSE_Linux_Enterprise_Server_15_x86_64'. Building repository 'SLE-Product-SLES15-Pool' cache ...........................................................................................................................................[done] Retrieving repository 'SLE-Product-SLES15-Updates' metadata ...................................................................................................................................[done] Building repository 'SLE-Product-SLES15-Updates' cache ........................................................................................................................................[done] Loading repository data... Reading installed packages... No matching items found. :~ # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh --+-------------------------------------------------------------------+----------------------------+---------+-----------+-------- 1 | Packages1 | Packages1 | Yes | (r ) Yes | No 2 | Pcakages-ser2 | Pcakages-ser2 | Yes | (r ) Yes | No 3 | SLES15-15-0 | SLES15-15-0 | Yes | (r ) Yes | Yes 4 | SUSE_Linux_Enterprise_Server_15_x86_64:SLE-Product-SLES15-Pool | SLE-Product-SLES15-Pool | Yes | (r ) Yes | No 5 | SUSE_Linux_Enterprise_Server_15_x86_64:SLE-Product-SLES15-Updates | SLE-Product-SLES15-Updates | Yes | (r ) Yes | Yes 6 | basesystem | basesystem | Yes | (r ) Yes | No 7 | development :~ # cat /etc/os-release NAME="SLES" VERSION="15" VERSION_ID="15" PRETTY_NAME="SUSE Linux Enterprise Server 15" ID="sles" ID_LIKE="suse" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:15" -----Original Message----- From: sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces at lists.suse.com] On Behalf Of Mike Marion Sent: Monday, November 6, 2017 8:22 PM To: Joe Doupnik Cc: sle-beta at lists.suse.com Subject: Re: [sle-beta] [resend] missing packages On Mon, Nov 06, 2017 at 04:53:59PM +0000, Joe Doupnik wrote: > Both UCX and libpcre2.8 are shown in YaST. The rest are not at my > end. As this is early in the beta program the missing may be on the to-do list. libpcre2.8 is in Desktop-Applications. I just ran into this myself. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.suse.com%2Fmailman%2Flistinfo%2Fsle-beta&data=02%7C01%7Ctalatb%40mellanox.com%7Cc01e48abb13e453fe4ef08d525433970%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636455893022234506&sdata=7lmevbEK4wH%2BehEXnAi%2B1drJZbuBph%2BTIfAEjJXP3JY%3D&reserved=0 From jrd at netlab1.net Mon Nov 6 11:50:49 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Mon, 6 Nov 2017 18:50:49 +0000 Subject: [sle-beta] [resend] missing packages In-Reply-To: References: <20171106182131.GR7333@qualcomm.com> Message-ID: <778e8b27-af08-c9ed-0237-e47df53e90f6@netlab1.net> ??? Try this combination in YaST, if your system permits: ??? Note the Desktop Applications Module, as also mentioned by Mike Marion. My YaST reports: and ??? Thanks, ??? Joe D. On 06/11/2017 18:36, Talat Batheesh wrote: > I'm using the Server distribution and I can't find it > > :~# zypper search libpcre2.8 > Refreshing service 'SUSE_Linux_Enterprise_Server_15_x86_64'. > Building repository 'SLE-Product-SLES15-Pool' cache ...........................................................................................................................................[done] > Retrieving repository 'SLE-Product-SLES15-Updates' metadata ...................................................................................................................................[done] > Building repository 'SLE-Product-SLES15-Updates' cache ........................................................................................................................................[done] > Loading repository data... > Reading installed packages... > No matching items found. > > > :~ # zypper lr > Repository priorities are without effect. All enabled repositories share the same priority. > > # | Alias | Name | Enabled | GPG Check | Refresh > --+-------------------------------------------------------------------+----------------------------+---------+-----------+-------- > 1 | Packages1 | Packages1 | Yes | (r ) Yes | No > 2 | Pcakages-ser2 | Pcakages-ser2 | Yes | (r ) Yes | No > 3 | SLES15-15-0 | SLES15-15-0 | Yes | (r ) Yes | Yes > 4 | SUSE_Linux_Enterprise_Server_15_x86_64:SLE-Product-SLES15-Pool | SLE-Product-SLES15-Pool | Yes | (r ) Yes | No > 5 | SUSE_Linux_Enterprise_Server_15_x86_64:SLE-Product-SLES15-Updates | SLE-Product-SLES15-Updates | Yes | (r ) Yes | Yes > 6 | basesystem | basesystem | Yes | (r ) Yes | No > 7 | development > > :~ # cat /etc/os-release > NAME="SLES" > VERSION="15" > VERSION_ID="15" > PRETTY_NAME="SUSE Linux Enterprise Server 15" > ID="sles" > ID_LIKE="suse" > ANSI_COLOR="0;32" > CPE_NAME="cpe:/o:suse:sles:15" > > > -----Original Message----- > From: sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces at lists.suse.com] On Behalf Of Mike Marion > Sent: Monday, November 6, 2017 8:22 PM > To: Joe Doupnik > Cc: sle-beta at lists.suse.com > Subject: Re: [sle-beta] [resend] missing packages > > On Mon, Nov 06, 2017 at 04:53:59PM +0000, Joe Doupnik wrote: > >> Both UCX and libpcre2.8 are shown in YaST. The rest are not at my >> end. As this is early in the beta program the missing may be on the to-do list. > libpcre2.8 is in Desktop-Applications. I just ran into this myself. > > -- > Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.suse.com%2Fmailman%2Flistinfo%2Fsle-beta&data=02%7C01%7Ctalatb%40mellanox.com%7Cc01e48abb13e453fe4ef08d525433970%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636455893022234506&sdata=7lmevbEK4wH%2BehEXnAi%2B1drJZbuBph%2BTIfAEjJXP3JY%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mcpnhkkpkhhhdakg.png Type: image/png Size: 66200 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: kejpphgpamhcecgm.png Type: image/png Size: 219545 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: adnaeicllhonbigf.png Type: image/png Size: 85862 bytes Desc: not available URL: From kukuk at suse.de Mon Nov 6 13:23:46 2017 From: kukuk at suse.de (Thorsten Kukuk) Date: Mon, 6 Nov 2017 21:23:46 +0100 Subject: [sle-beta] xinetd question In-Reply-To: References: Message-ID: <20171106202346.GA6296@suse.de> On Mon, Nov 06, Sherry Crandall wrote: > I saw in a previous email the xinetd is no longer provided. Our engineers have > used it to set up a tftp server in the past. They are asking how to set up a > tfpt server without xinetd. They thought it was a requirement. systemctl enable tftp.socket or systemctl enable tftp.service There is really no need anymore for xinetd. Between, the above is already the default for SLES12 and not new. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From fcrozat at suse.com Tue Nov 7 01:22:25 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 07 Nov 2017 09:22:25 +0100 Subject: [sle-beta] missing packages In-Reply-To: References: Message-ID: <1510042945.5845.218.camel@suse.com> Le dimanche 05 novembre 2017 ? 09:55 +0200, Talat mellanox a ?crit?: > Hi everyone, > > We can't find the following packages in first beta of SLES-15-Server > perftest package please open a bug report > libibverbs-dev in order to install perftest package. will be pulled when perftest is added > rpm-build package Will be fixed in next beta > libvma package > libreswan package > strongswan package > linuxptp package > UCX package open a bug report for those missing package (you can open a single bug report for all the missing package at once). >? -- Frederic Crozat Enterprise Desktop Release Manager SUSE From jrd at netlab1.net Tue Nov 7 02:35:32 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Tue, 7 Nov 2017 09:35:32 +0000 Subject: [sle-beta] xinetd question In-Reply-To: <20171106202346.GA6296@suse.de> References: <20171106202346.GA6296@suse.de> Message-ID: <37470502-8212-3add-f4ea-90a1fa5e21b1@netlab1.net> On 06/11/2017 20:23, Thorsten Kukuk wrote: > On Mon, Nov 06, Sherry Crandall wrote: > >> I saw in a previous email the xinetd is no longer provided. Our engineers have >> used it to set up a tftp server in the past. They are asking how to set up a >> tfpt server without xinetd. They thought it was a requirement. > systemctl enable tftp.socket > > or > > systemctl enable tftp.service > > There is really no need anymore for xinetd. > Between, the above is already the default for SLES12 and not new. > > Thorsten. --------- ??? While chasing down the details of this one may ask about how this works if one had to create a new service. In that chase one comes across a reference to man page? systemd.service(7)? which seems to be a key item. Alas, if one tries to read it we quickly discover the authors don't understand reading, only writing beyond the right margin, and we are left almost stranded. Try ? man 7 systemd.service?? to check this yourself. Similarly, discovering what "services" are on offer is carefully hidden from the view of mere mortals, so YaST is our easiest source of clues. Methinks we need a Siri module/oracle to ask about serious matters. ??? We are also left wondering about the IP access controls in xinetd items. They appear to be omitted in the systemd jungle (meaning scattered widely, obscured visibility, torturous terrain). That means we must revert to direct control in IPtables, which we can do. ??? This seems to be another instance of missing the goal of usability. Curiously, SUSE has done a sterling job (quality and cost) about usability with YaST and module installation, first rate, far beyond efforts by other vendors, and that counts. Yet there is a lack of suitable documentation to readily surmount present difficulties (see yesterday's "bridge over troubled waters"). I think there needs to be more bridge building, else we will be stranded on the far side searching for alternatives. ??? Thanks, ??? Joe D. From talatb at mellanox.com Tue Nov 7 03:12:44 2017 From: talatb at mellanox.com (Talat mellanox) Date: Tue, 7 Nov 2017 12:12:44 +0200 Subject: [sle-beta] missing packages In-Reply-To: <1510042945.5845.218.camel@suse.com> References: <1510042945.5845.218.camel@suse.com> Message-ID: Thank you. On Tue, Nov 7, 2017 at 10:22 AM, Frederic Crozat wrote: > Le dimanche 05 novembre 2017 ? 09:55 +0200, Talat mellanox a ?crit : > > Hi everyone, > > > > We can't find the following packages in first beta of SLES-15-Server > > perftest package > > please open a bug report > > opened bug 1066859 > > libibverbs-dev in order to install perftest package. > will be pulled when perftest is added > > > rpm-build package > > Will be fixed in next beta > > > libvma package > > libreswan package > > strongswan package > > linuxptp package > > UCX package > > open a bug report for those missing package (you can open a single bug > report for all the missing package at once). > > opened a bug on all of the above missing packages, I'll appreciate it if this issue will be resolved in the next beta in order to start test the RDMA/Infiniband. > > -- > Frederic Crozat > Enterprise Desktop Release Manager > SUSE > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmarion at qualcomm.com Tue Nov 7 10:24:00 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Tue, 7 Nov 2017 17:24:00 +0000 Subject: [sle-beta] [resend] missing packages In-Reply-To: References: Message-ID: <20171107172359.GW7333@qualcomm.com> On Mon, Nov 06, 2017 at 04:43:56PM +0000, Talat Batheesh wrote: > We can't find the following packages in first beta of SLES-15-Server Maybe I just missed it (pretty sure I dug around in all the ISOs) but rpm-build is missing as well. I actually copied rpmbuild and the needed libs from a 12.3 host, to build it from the rpm src.rpm. Fun. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From donald.buchholz at intel.com Tue Nov 7 10:33:44 2017 From: donald.buchholz at intel.com (Don Buchholz) Date: Tue, 7 Nov 2017 09:33:44 -0800 Subject: [sle-beta] SLE15(Beta1) and zypper ... In-Reply-To: <20171030194843.GA16155@suse.de> References: <20171030194843.GA16155@suse.de> Message-ID: On 10/30/2017 12:48 PM, Thorsten Kukuk wrote: > On Mon, Oct 30, Don Buchholz wrote: >> Hi, >> >> With the new "Installer" and "Packages" ISOs paradigm, >> itappears the zypper repository configuration has been >> extended. > That's really very, very old stuff, nothing new. > > Thorsten Ah, OK. Thanks. I'm a bit new to the SLE universe. I'll just continue to manipulate the *.repo files then. - Don From donald.buchholz at intel.com Tue Nov 7 10:55:32 2017 From: donald.buchholz at intel.com (Don Buchholz) Date: Tue, 7 Nov 2017 09:55:32 -0800 Subject: [sle-beta] problems with console video? Message-ID: <46cafe33-bf9f-ea72-da1a-ceaf7f780052@intel.com> My early installs have been to a VM (running on a KVM virtualization host) and no problems in that configuration. However, when I try and install onto an actual Dell R-730, I get no video. It doesn't matter if I try and use a text or graphical console. # systemctl set-default [multi-user|graphical].target I have even tried to force the video mode to 1024x768 by adding the kernel param "vga=0x0305" in the grub.cfg file. (It fixed another system using a different Linux distro ... figured it was worth a try here.) I am using an older Raritan Dominion-II KVM system and the dongles which attach to the host do not have valid EDID data. As the system begins to boot, I can see Grub, and see initial messages from the kernel. I see the video resize to 1024x768, and then messages up to somewhere near the "Console: switching to colour dummy device 80x25". Has anyone else had similar problems? - Don Buchholz From scottx.register at intel.com Tue Nov 7 12:28:41 2017 From: scottx.register at intel.com (Register, ScottX) Date: Tue, 7 Nov 2017 19:28:41 +0000 Subject: [sle-beta] problems with console video? In-Reply-To: <46cafe33-bf9f-ea72-da1a-ceaf7f780052@intel.com> References: <46cafe33-bf9f-ea72-da1a-ceaf7f780052@intel.com> Message-ID: <1DD97F252888F94BB0FC25E64E6807792EE09EFE@ORSMSX111.amr.corp.intel.com> > -----Original Message----- > From: sle-beta-bounces at lists.suse.com [mailto:sle-beta- > bounces at lists.suse.com] On Behalf Of Don Buchholz > Sent: Tuesday, November 7, 2017 9:56 AM > To: sle-beta at lists.suse.com > Subject: [sle-beta] problems with console video? > > My early installs have been to a VM (running on a KVM virtualization host) > and no problems in that configuration. > > Has anyone else had similar problems? > > - Don Buchholz > We had the same issue with r730s w/ Raritan kvm dongles. Solution was to edit the kernel boot parameters via grub and add "nomodeset". Scott From donald.buchholz at intel.com Tue Nov 7 13:33:25 2017 From: donald.buchholz at intel.com (Don Buchholz) Date: Tue, 7 Nov 2017 12:33:25 -0800 Subject: [sle-beta] problems with console video? In-Reply-To: <1DD97F252888F94BB0FC25E64E6807792EE09EFE@ORSMSX111.amr.corp.intel.com> References: <46cafe33-bf9f-ea72-da1a-ceaf7f780052@intel.com> <1DD97F252888F94BB0FC25E64E6807792EE09EFE@ORSMSX111.amr.corp.intel.com> Message-ID: <2a79e238-e2b5-6ed1-06a9-413c68339f1f@intel.com> On 11/07/2017 11:28 AM, Register, ScottX wrote: >> -----Original Message----- >> From: sle-beta-bounces at lists.suse.com [mailto:sle-beta- >> bounces at lists.suse.com] On Behalf Of Don Buchholz >> Sent: Tuesday, November 7, 2017 9:56 AM >> To: sle-beta at lists.suse.com >> Subject: [sle-beta] problems with console video? >> >> My early installs have been to a VM (running on a KVM virtualization host) >> and no problems in that configuration. >> >> Has anyone else had similar problems? >> >> - Don Buchholz >> > We had the same issue with r730s w/ Raritan kvm dongles. > Solution was to edit the kernel boot parameters via grub and add "nomodeset". > > Scott Thanks, Scott! Yup. That fixed it. It wasn't just the Raritan dongles with issues. I plugged a monitor directly into the back and still had the problem. Found "nomodeset" worked with the direct-attach monitor and wanted to verify it also fixed the problem with the Raritan hardware, too, before posting back to this list. (It does, both text and X11 consoles are now working with Raritan system.) I suppose I should file a bug so one of SUSE's engineers can give this some attention ... Cheers! - Don From mmarion at qualcomm.com Tue Nov 7 19:05:58 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Wed, 8 Nov 2017 02:05:58 +0000 Subject: [sle-beta] Heads up if you use openafs at all Message-ID: <20171108020557.GB14031@qualcomm.com> ...or anything else that has a kernel module and calls page_cache_alloc_cold I tried, in vain, to build openafs on Beta1.. it turns out Suse has patched out the page_cache_alloc_cold function from the kernel. See patch file suse/patches.suse/mm-remove-__GFP_COLD.patch (or link http://lkml.kernel.org/r/20171018075952.10627-9-mgorman at techsingularity.net) The reasoning and such makes sense, but it's not in mainline yet so anything out there with kernel modules that you're used to building that requires this, isn't going to build. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From jsrain at suse.cz Tue Nov 7 23:50:57 2017 From: jsrain at suse.cz (Jiri Srain) Date: Wed, 8 Nov 2017 07:50:57 +0100 Subject: [sle-beta] SLE15(Beta1) and zypper ... In-Reply-To: References: Message-ID: <5ae9e056-34a8-ad61-7c19-ee4e338da58b@suse.cz> On 30.10.2017 19:55, Don Buchholz wrote: > Hi, > > With the new "Installer" and "Packages" ISOs paradigm, > itappears the zypper repository configuration has been > extended. > > Using "zypper lr -d", I see the base system repository > from the 'Installer' ISO, and then the four additional > modules. > > ?| sle15:~# zypper lr -d |cut -c1-2,4-37,39-51,105-150 > ?|?? ... > ?|# | Alias?????????????????????????? | Name?????? | URI > ?|--+---------------------------------+------------+--------------------------------------------- > > ?|? 1| Basesystem-Module_15-0????????? | SLE15-Pkg? | > http://SLE-SRV/distros/suse/ia32e/sle15-pkg/ > ?|? 2| Desktop-Applications-Module_15-0| SLE15-Pkg? | > http://SLE-SRV/distros/suse/ia32e/sle15-pkg/ > ?| 3| Development-Tools-Module_15-0?? | SLE15-Pkg? | > http://SLE-SRV/distros/suse/ia32e/sle15-pkg/ > ?|? 4| Legacy-Module_15-0????????????? | SLE15-Pkg? | > http://SLE-SRV/distros/suse/ia32e/sle15-pkg/ > ?|? 5| SLES15-15-0???????????????????? | SLES15-15-0| > http://SLE-SRV/distros/suse/ia32e/sle15 > > What I find interesting here is that the Installer > [SLES15-15-0] repository has it's own URI, but then > the added modules all share a common URI!? Looking > at the configuration files in /etc/zypp/repos.d/ > I see there is a "path=...." parameter being added > to "baseurl=....".? Only 'baseurl' is visible when > using "zypper listrepo" and I can not find an option > to list the full URL to the package repository. To give you the reason for this: If you use a single DVD (or ISO image) with multiple repositories, libzypp needs to be able to identify the media itself (e.g. to ask you to put a specific DVD to the drive). If you have all repositories on an on-line source like HTTP server, you can follow this mechanism (and copy the whole DVD) or point libzypp to individual repositories without the path- parameter. Jiri > Looking at an SLES12-SP3 system, I do see the > "path=..." param in the installer-created > "SLES12-SP3-12.3-0.repo", but it is not present > in *.repo files created with "zypper addrepo ...". > > Am I missing something in the zypper man page? > Or does zypper(8) need to be extended to list the > added paths?? Or should I just plan on forgoing > command-line examination/creation of repositories > and just continue to manipulate the *.repo files > directly? > > Regards, > - Don Buchholz > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Krizikova 148/34 tel: +420 284 084 659 186 00 Praha 8 fax: +420 284 084 001 Czech Republic http://www.suse.com From mnowak at suse.com Wed Nov 8 02:15:00 2017 From: mnowak at suse.com (Michal Nowak) Date: Wed, 8 Nov 2017 10:15:00 +0100 Subject: [sle-beta] problems to boot/install sle12 on an VirtualBox system In-Reply-To: References: Message-ID: <7a268aaf-23b2-1f33-044b-e7807ba1b902@suse.com> On 08/11/17 08:42, Wolf, Matthias wrote: > Hi, > > i download the first dvd and checksum is ok, but I can not boot from > install medium in an VirtualBox VM. > > Error MSG: > > FATAL: Could not read from the boot medium! System hated. > > Other iso`s works fine L > > It`s also possible to mount the iso on an linux system (also VirtualBox VM). > > Have someone else the same Problems? > > THX > > Matthias Hello Matthias, I just successfully installed SLES15 from Beta1 ISO medium in VirtualBox 5.1.30 from openSUSE repositories. Can it be that your "Could not read from the boot medium" problem is more of a file permissions problem on the host? Do you have read permission on the ISO file on the host? Do the file permissions of the Beta1 image differ to permissions of images which work for you? Michal From mgorman at suse.com Wed Nov 8 02:21:22 2017 From: mgorman at suse.com (Mel Gorman) Date: Wed, 8 Nov 2017 09:21:22 +0000 Subject: [sle-beta] Heads up if you use openafs at all In-Reply-To: <20171108020557.GB14031@qualcomm.com> References: <20171108020557.GB14031@qualcomm.com> Message-ID: <20171108092122.rmhnbxnxgfcvwr6d@novell.com> On Wed, Nov 08, 2017 at 02:05:58AM +0000, Mike Marion wrote: > ...or anything else that has a kernel module and calls > page_cache_alloc_cold > > I tried, in vain, to build openafs on Beta1.. it turns out Suse has > patched out the page_cache_alloc_cold function from the kernel. See > patch file suse/patches.suse/mm-remove-__GFP_COLD.patch (or link > http://lkml.kernel.org/r/20171018075952.10627-9-mgorman at techsingularity.net) > > The reasoning and such makes sense, but it's not in mainline yet so > anything out there with kernel modules that you're used to building that > requires this, isn't going to build. > Hi Mike, Ultimately, we expect drivers using the function to convert as the patches in question are expected to be included in 4.15. There are numerous potential workarounds. One could add a simple #define page_cache_alloc_cold(x) page_cache_alloc(x) to one of the headers of the affected out-of-tree module until it can detect the presense of the API. Another is to apply the patch below to the local kernel headers. It'll trigger a deprecated warning encourging driver authors to convert. If this is a persistent problem, I can merge the patch to SLE-15 which we can carry for at least one release. I hope this helps diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h index 18b022823b47..7130c4213e05 100644 --- a/include/linux/pagemap.h +++ b/include/linux/pagemap.h @@ -214,6 +214,12 @@ static inline struct page *page_cache_alloc(struct address_space *x) return __page_cache_alloc(mapping_gfp_mask(x)); } +static inline __deprecated +struct page *page_cache_alloc_cold(struct address_space *x) +{ + return page_cache_alloc(x); +} + static inline gfp_t readahead_gfp_mask(struct address_space *x) { return mapping_gfp_mask(x) | __GFP_NORETRY | __GFP_NOWARN; -- Mel Gorman SUSE Labs From okurz at suse.de Wed Nov 8 06:36:55 2017 From: okurz at suse.de (Oliver Kurz) Date: Wed, 08 Nov 2017 14:36:55 +0100 Subject: [sle-beta] Another missing package In-Reply-To: References: Message-ID: <1673231.7xj63ec8zG@linux-28d6.suse> On Wednesday, 8 November 2017 14:12:47 CET Sherry Crandall wrote: > We can't find minicom. Is it gone, or will it show up later? Currently it is not available as a SLE15 package. Please provide a bug report. Regards, Oliver Kurz From fcrozat at suse.com Wed Nov 8 07:17:10 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Wed, 08 Nov 2017 15:17:10 +0100 Subject: [sle-beta] [resend] missing packages In-Reply-To: <20171107172359.GW7333@qualcomm.com> References: <20171107172359.GW7333@qualcomm.com> Message-ID: <1510150630.5845.236.camel@suse.com> Le mardi 07 novembre 2017 ? 17:24 +0000, Mike Marion a ?crit?: > On Mon, Nov 06, 2017 at 04:43:56PM +0000, Talat Batheesh wrote: > > > > > We can't find the following packages in first beta of SLES-15- > > Server > > Maybe I just missed it (pretty sure I dug around in all the ISOs) but > rpm-build is missing as well.??I actually copied rpmbuild and the > needed > libs from a 12.3 host, to build it from the rpm src.rpm.??Fun. As already reported by somebody else on the mailing list, it is known issue and will be fixed with beta2. -- Frederic Crozat Enterprise Desktop Release Manager SUSE From mmarion at qualcomm.com Wed Nov 8 08:37:14 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Wed, 8 Nov 2017 15:37:14 +0000 Subject: [sle-beta] Heads up if you use openafs at all In-Reply-To: <20171108092122.rmhnbxnxgfcvwr6d@novell.com> References: <20171108020557.GB14031@qualcomm.com> <20171108092122.rmhnbxnxgfcvwr6d@novell.com> Message-ID: <20171108153713.GD14031@qualcomm.com> On Wed, Nov 08, 2017 at 09:21:22AM +0000, Mel Gorman wrote: > Ultimately, we expect drivers using the function to convert as the > patches in question are expected to be included in 4.15. There are > numerous potential workarounds. One could add a simple > > #define page_cache_alloc_cold(x) page_cache_alloc(x) Thanks, I was going to try something like that. I just wanted to warn people that might also be compiling things with kernel modules so they wouldn't have to spend the time finding the cause. I assume openafs' module bits will be updated after the mainline kernel accepts the change. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From mmarion at qualcomm.com Wed Nov 8 09:40:32 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Wed, 8 Nov 2017 16:40:32 +0000 Subject: [sle-beta] Heads up if you use openafs at all In-Reply-To: <20171108153713.GD14031@qualcomm.com> References: <20171108020557.GB14031@qualcomm.com> <20171108092122.rmhnbxnxgfcvwr6d@novell.com> <20171108153713.GD14031@qualcomm.com> Message-ID: <20171108164031.GF14031@qualcomm.com> On Wed, Nov 08, 2017 at 03:37:14PM +0000, Mike Marion wrote: > Thanks, I was going to try something like that. I just wanted to warn > people that might also be compiling things with kernel modules so they > wouldn't have to spend the time finding the cause. I assume openafs' > module bits will be updated after the mainline kernel accepts the > change. Turns out.. ditto for patches.suse/mm-pagevec-remove-cold-parameter-for-pagevecs.patch Which removes the int cold parameter. This is an easy search and replace of the ,0 in any calls though. I see why this was made as well because every call I see anywhere is always ,0 so, as the patch says: The parameter is removed simply because it is a bit stupid to have a useless parameter copied everywhere. I love the brutal honesty. :) -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From donald.buchholz at intel.com Wed Nov 8 15:23:41 2017 From: donald.buchholz at intel.com (Don Buchholz) Date: Wed, 8 Nov 2017 14:23:41 -0800 Subject: [sle-beta] dracut 'systemd-bootchart' missing? Message-ID: <9f21612c-2c2e-d5d8-9eb6-72e5ffd84b71@intel.com> I was building/installing a new driver, and the "make install" step builds a new 'initrd' by calling "dracut --force". # make install ...... Running depmod... Updating initrd... dracut: Executing: /usr/bin/dracut --force dracut: dracut module 'systemd-bootchart' will not be installed, because command '/usr/lib/systemd/systemd-bootchart' could not be found! dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found! Failed to look up reference node - returned empty list ...... Has anyone else seen this? -------------- next part -------------- An HTML attachment was scrubbed... URL: From talatb at mellanox.com Thu Nov 9 01:08:48 2017 From: talatb at mellanox.com (Talat mellanox) Date: Thu, 9 Nov 2017 10:08:48 +0200 Subject: [sle-beta] yast2 system-clone is missing Message-ID: Hi, We can't auto install the SLES 15 Server image since we didn't know how to generate the yast answer file, could you please assist with the following? - Provide a working yast file(answer file) or explain how to generate it on an already installed machine. - Provide a guide on PXE deployment with the ?Packages? iso , as the current guide doesn?t have any real info, we would like the pxelinux syntax /params etc. Basically, ?yast2 system-clone? is missing, so can?t generate autoyast answer file, and hence cannot autoinstall. Yours, Talat -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Thu Nov 9 02:49:13 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 9 Nov 2017 10:49:13 +0100 Subject: [sle-beta] problems with console video? In-Reply-To: <2a79e238-e2b5-6ed1-06a9-413c68339f1f@intel.com> References: <46cafe33-bf9f-ea72-da1a-ceaf7f780052@intel.com> <1DD97F252888F94BB0FC25E64E6807792EE09EFE@ORSMSX111.amr.corp.intel.com> <2a79e238-e2b5-6ed1-06a9-413c68339f1f@intel.com> Message-ID: <34438A20-D39D-4F63-9051-F9206D873D9E@suse.com> Hi, > On 7 Nov 2017, at 21:33, Don Buchholz wrote: > I suppose I should file a bug so one of SUSE's > engineers can give this some attention ? I didn?t find any bug related to this issue, could you please open a bug report? Thanks, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From vmoutoussamy at suse.com Thu Nov 9 03:02:15 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 9 Nov 2017 11:02:15 +0100 Subject: [sle-beta] xinetd question In-Reply-To: <37470502-8212-3add-f4ea-90a1fa5e21b1@netlab1.net> References: <20171106202346.GA6296@suse.de> <37470502-8212-3add-f4ea-90a1fa5e21b1@netlab1.net> Message-ID: <722077E5-34DE-47FF-872C-2251AB356341@suse.com> Hi, > On 7 Nov 2017, at 10:35, Joe Doupnik wrote: > --------- > While chasing down the details of this one may ask about how this works if one had to create a new service. In that chase one comes across a reference to man page systemd.service(7) which seems to be a key item. Alas, if one tries to read it we quickly discover the authors don't understand reading, only writing beyond the right margin, and we are left almost stranded. Try man 7 systemd.service to check this yourself. Similarly, discovering what "services" are on offer is carefully hidden from the view of mere mortals, so YaST is our easiest source of clues. Methinks we need a Siri module/oracle to ask about serious matters. > We are also left wondering about the IP access controls in xinetd items. They appear to be omitted in the systemd jungle (meaning scattered widely, obscured visibility, torturous terrain). That means we must revert to direct control in IPtables, which we can do. > This seems to be another instance of missing the goal of usability. Curiously, SUSE has done a sterling job (quality and cost) about usability with YaST and module installation, first rate, far beyond efforts by other vendors, and that counts. Yet there is a lack of suitable documentation to readily surmount present difficulties (see yesterday's "bridge over troubled waters"). I think there needs to be more bridge building, else we will be stranded on the far side searching for alternatives. > Thanks, > Joe D. There is a bug report related to man pages: https://bugzilla.suse.com/show_bug.cgi?id=1066980 but it?s related to formatting issue. So if you find some missing pieces in the manpages, please create a dedicated bug report and specify what you think can help you or other. Of course documentations and manpages are really important for us, and your input can help us improve here. Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From ronald.j.bynoe at intel.com Thu Nov 9 09:53:18 2017 From: ronald.j.bynoe at intel.com (Bynoe, Ronald J) Date: Thu, 9 Nov 2017 16:53:18 +0000 Subject: [sle-beta] Another missing package In-Reply-To: References: <1673231.7xj63ec8zG@linux-28d6.suse> Message-ID: <1510246395.16632.6.camel@intel.com> For reference, SLES15 Beta 1 is also missing cgdcbxd, libcgroup1, and libcgroup-tools, we filed a BZ for the missing packages: https://bugzilla.suse.com/show_bug.cgi?id=1067489 Pleasantly, Ronald Bynoe ND SW: IP Development QoS and Drivers Linux Validation Lead On Thu, 2017-11-09 at 10:39 +0100, Vincent Moutoussamy wrote: Hi, Just for reference, here is the bugzilla report: https://bugzilla.suse.com/show_bug.cgi?id=1067183 Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager On 8 Nov 2017, at 14:36, Oliver Kurz > wrote: On Wednesday, 8 November 2017 14:12:47 CET Sherry Crandall wrote: We can't find minicom. Is it gone, or will it show up later? Currently it is not available as a SLE15 package. Please provide a bug report. Regards, Oliver Kurz _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From donald.buchholz at intel.com Thu Nov 9 09:59:38 2017 From: donald.buchholz at intel.com (Don Buchholz) Date: Thu, 9 Nov 2017 08:59:38 -0800 Subject: [sle-beta] problems with console video? In-Reply-To: <34438A20-D39D-4F63-9051-F9206D873D9E@suse.com> References: <46cafe33-bf9f-ea72-da1a-ceaf7f780052@intel.com> <1DD97F252888F94BB0FC25E64E6807792EE09EFE@ORSMSX111.amr.corp.intel.com> <2a79e238-e2b5-6ed1-06a9-413c68339f1f@intel.com> <34438A20-D39D-4F63-9051-F9206D873D9E@suse.com> Message-ID: <2193626f-7a05-35ff-97d9-945b726638ef@intel.com> On 11/09/2017 01:49 AM, Vincent Moutoussamy wrote: > Hi, >> On 7 Nov 2017, at 21:33, Don Buchholz > > wrote: > >> I suppose I should file a bug so one of SUSE's >> engineers can give this some attention ? > > I didn?t find any bug related to this issue, could you > please open a bug report? > > Thanks, > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program and SDK Project Manager Done. -- https://bugzilla.suse.com/show_bug.cgi?id=1067490 - Don -------------- next part -------------- An HTML attachment was scrubbed... URL: From aginies at suse.com Thu Nov 9 13:47:20 2017 From: aginies at suse.com (Antoine Ginies) Date: Thu, 9 Nov 2017 21:47:20 +0100 Subject: [sle-beta] More on missing packages In-Reply-To: References: Message-ID: <20171109204720.GA600@linux-w541.guibland.com> Sherry Crandall: > We imported the following from OpenSUSE:Factory to get our OBS scripts to work. Will these be provided in beta2? Maybe they are all part of the rpmbuild package, which I know has already been reported as missing. > > > aaa_base-13.2+git20170828.8f12a9e-1.2.x86_64.rpm dwz-0.12-3.8.x86_64.rpm > > aaa_base-extras-13.2+git20170828.8f12a9e-1.2.x86_64.rpm extract-appdata-icons-2016.05.04-1.3.noarch.rpm > > aaa_base-malloccheck-13.2+git20170828.8f12a9e-1.2.x86_64.rpm kernel-obs-build-4.13.11-1.1.x86_64.rpm > > brp-check-suse-84.87+git20170602.cec5415-1.2.x86_64.rpm post-build-checks-84.87+git20170929.5b244d1-1.1.noarch.rpm > > brp-extract-appdata-2016.05.04-1.3.noarch.rpm rpm-4.13.0.1-9.1.x86_64.rpm > > build-20171023-1.1.noarch.rpm rpm-build-4.13.0.1-9.1.x86_64.rpm > > build-compare-20171020T085619.7cef93b-1.1.noarch.rpm rpm-devel-4.13.0.1-9.1.x86_64.rpm > > build-initvm-x86_64-20171023-1.1.noarch.rpm rpmlint-1.10-3.1.noarch.rpm > > build-mkbaselibs-20171023-1.1.noarch.rpm rpmlint-Factory-1.0-92.1.noarch.rpm > > build-mkbaselibs-sle-20171023-1.1.noarch.rpm rpmlint-Factory-strict-1.0-92.1.noarch.rpm > > build-mkdrpms-20171023-1.1.noarch.rpm hello, Thanks for the report. - following is the list of packages already planned to have in next milestone: build-mkdrpms aaa_base dwz aaa_base-extras brp-check-suse build-2017 rpm-build build-compare rpm-devel build-initvm-x86_64 rpmlint build-mkbaselibs - so they are still missing some missing in the list: kernel-obs-build brp-extract-appdata post-build-checks rpmlint-Factory rpmlint-Factory-strict build-mkbaselibs-sle Please open a bug so we can track that properly. Regards, Antoine > > Thanks, > Sherry > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -- Antoine Ginies Release/Project Manager SUSE France From dkohler at cray.com Thu Nov 9 15:47:27 2017 From: dkohler at cray.com (David Kohler) Date: Thu, 9 Nov 2017 22:47:27 +0000 Subject: [sle-beta] yast2 system-clone is missing In-Reply-To: References: Message-ID: I thought it was `yast2 clone_system`. From: sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces at lists.suse.com] On Behalf Of Talat mellanox Sent: Thursday, November 09, 2017 2:09 AM To: sle-beta at lists.suse.com Cc: noas at mellanox.com; noamd at mellanox.com Subject: [sle-beta] yast2 system-clone is missing Hi, We can't auto install the SLES 15 Server image since we didn't know how to generate the yast answer file, could you please assist with the following? * Provide a working yast file(answer file) or explain how to generate it on an already installed machine. * Provide a guide on PXE deployment with the ?Packages? iso , as the current guide doesn?t have any real info, we would like the pxelinux syntax /params etc. Basically, ?yast2 system-clone? is missing, so can?t generate autoyast answer file, and hence cannot autoinstall. Yours, Talat -------------- next part -------------- An HTML attachment was scrubbed... URL: From fcrozat at suse.com Fri Nov 10 02:28:45 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Fri, 10 Nov 2017 10:28:45 +0100 Subject: [sle-beta] dracut 'systemd-bootchart' missing? In-Reply-To: <9f21612c-2c2e-d5d8-9eb6-72e5ffd84b71@intel.com> References: <9f21612c-2c2e-d5d8-9eb6-72e5ffd84b71@intel.com> Message-ID: <1510306125.8872.0.camel@suse.com> Le mercredi 08 novembre 2017 ? 14:23 -0800, Don Buchholz a ?crit?: > I was building/installing a new driver, and the "make install" > step builds a new 'initrd' by calling "dracut --force". > # make install > ?...... > Running depmod... > Updating initrd... > dracut: Executing: /usr/bin/dracut --force > dracut: dracut module 'systemd-bootchart' will not be installed, > because command '/usr/lib/systemd/systemd-bootchart' could not be > found! > dracut: dracut module 'dmraid' will not be installed, because command > 'dmraid' could not be found! > Failed to look up reference node - returned empty list > ?...... > Has anyone else seen this?? systemd-bootchart is not longer part of systemd anymore, this is why. Please open a bug report, we need to ensure dracut doesn't complain when it isn't available. -- Frederic Crozat Enterprise Desktop Release Manager SUSE From donald.buchholz at intel.com Fri Nov 10 10:07:01 2017 From: donald.buchholz at intel.com (Don Buchholz) Date: Fri, 10 Nov 2017 09:07:01 -0800 Subject: [sle-beta] dracut 'systemd-bootchart' missing? In-Reply-To: <1510306125.8872.0.camel@suse.com> References: <9f21612c-2c2e-d5d8-9eb6-72e5ffd84b71@intel.com> <1510306125.8872.0.camel@suse.com> Message-ID: <8bb4c3f4-c556-3990-f618-2f01501c59dc@intel.com> On 11/10/2017 01:28 AM, Frederic Crozat wrote: > Le mercredi 08 novembre 2017 ? 14:23 -0800, Don Buchholz a ?crit : >> I was building/installing a new driver, and the "make install" >> step builds a new 'initrd' by calling "dracut --force". >> # make install >> ...... >> Running depmod... >> Updating initrd... >> dracut: Executing: /usr/bin/dracut --force >> dracut: dracut module 'systemd-bootchart' will not be installed, >> because command '/usr/lib/systemd/systemd-bootchart' could not be >> found! >> dracut: dracut module 'dmraid' will not be installed, because command >> 'dmraid' could not be found! >> Failed to look up reference node - returned empty list >> ...... >> Has anyone else seen this? > systemd-bootchart is not longer part of systemd anymore, this is why. > > Please open a bug report, we need to ensure dracut doesn't complain > when it isn't available. > OK. Bug has been edited to include "dracut" in the title/summary. -- https://bugzilla.suse.com/show_bug.cgi?id=1067279 From beta-programs at lists.suse.com Fri Nov 10 13:21:13 2017 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Fri, 10 Nov 2017 21:21:13 +0100 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 2! Message-ID: <5a060a39947ab_4440d9b3187057a@boucane.mail> Two weeks after Beta 1, We are happy to announce Beta 2 of SUSE Linux Enterprise 15: SUSE Linux Enterprise Server (SLES), SUSE Linux Enterprise Desktop (SLED), SUSE Linux Enterprise High Availability (SLE-HA), and SUSE Linux Enterprise Workstation Extension (SLE-WE) Download[1] == More information SLE Beta Page[2] Release Notes[3] Kniwn Issues[4] Your SUSE Linux Enterprise Team == Beta Program Please refer to our dedicated SLE Beta Program webpage[1] for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/sle-beta/#download -------------- next part -------------- An HTML attachment was scrubbed... URL: From talatb at mellanox.com Sun Nov 12 01:03:11 2017 From: talatb at mellanox.com (Talat mellanox) Date: Sun, 12 Nov 2017 10:03:11 +0200 Subject: [sle-beta] yast2 system-clone is missing In-Reply-To: References: Message-ID: On Fri, Nov 10, 2017 at 12:47 AM, David Kohler wrote: > I thought it was `yast2 clone_system`. > Right, was my mistake. So yast2 clone_system is missing, Any help ?? Is this tool included in Beta? > > > *From:* sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces@ > lists.suse.com] *On Behalf Of *Talat mellanox > *Sent:* Thursday, November 09, 2017 2:09 AM > *To:* sle-beta at lists.suse.com > *Cc:* noas at mellanox.com; noamd at mellanox.com > *Subject:* [sle-beta] yast2 system-clone is missing > > > > Hi, > > > > We can't auto install the SLES 15 Server image since we didn't know how to > generate the yast answer file, could you please assist with the following? > > - Provide a working yast file(answer file) or explain how to generate > it on an already installed machine. > - Provide a guide on PXE deployment with the ?Packages? iso , as the > current guide doesn?t have any real info, we would like the pxelinux syntax > /params etc. > > > > Basically, ?yast2 system-clone? is missing, so can?t generate autoyast > answer file, and hence cannot autoinstall. > > > > > > Yours, > > Talat > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kukuk at suse.de Sun Nov 12 01:12:23 2017 From: kukuk at suse.de (Thorsten Kukuk) Date: Sun, 12 Nov 2017 09:12:23 +0100 Subject: [sle-beta] yast2 system-clone is missing In-Reply-To: References: Message-ID: <20171112081223.GA26059@suse.de> On Sun, Nov 12, Talat mellanox wrote: > So yast2 clone_system is missing, Any help ??? Yes, looks like you did not install it, so just install it ;) > Is this tool included in Beta? Yes, it is: zypper in autoyast2-installation Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From talatb at mellanox.com Sun Nov 12 02:55:19 2017 From: talatb at mellanox.com (Talat mellanox) Date: Sun, 12 Nov 2017 11:55:19 +0200 Subject: [sle-beta] yast2 system-clone is missing In-Reply-To: <20171112081223.GA26059@suse.de> References: <20171112081223.GA26059@suse.de> Message-ID: it is already installed, ok i will try with BETA2 and update. On Sun, Nov 12, 2017 at 10:12 AM, Thorsten Kukuk wrote: > On Sun, Nov 12, Talat mellanox wrote: > > > So yast2 clone_system is missing, Any help ?? > > Yes, looks like you did not install it, so just install it ;) > > > Is this tool included in Beta? > > Yes, it is: > zypper in autoyast2-installation > > Thorsten > > -- > Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany > GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG > Nuernberg) > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kukuk at suse.de Sun Nov 12 04:20:08 2017 From: kukuk at suse.de (Thorsten Kukuk) Date: Sun, 12 Nov 2017 12:20:08 +0100 Subject: [sle-beta] yast2 system-clone is missing In-Reply-To: References: <20171112081223.GA26059@suse.de> Message-ID: <20171112112008.GA5400@suse.de> On Sun, Nov 12, Talat mellanox wrote: > it is already installed, > ok i will try with BETA2 and update. autoyast2-installation is installed and yast2 clone_system does not work? What is the error message? Sure you didn't mix up with "autoyast2"? Thorsten > > > On Sun, Nov 12, 2017 at 10:12 AM, Thorsten Kukuk wrote: > > On Sun, Nov 12, Talat mellanox wrote: > > > So yast2 clone_system is missing, Any help ??? > > Yes, looks like you did not install it, so just install it ;) > > > Is this tool included in Beta? > > Yes, it is: > zypper in autoyast2-installation > > ? Thorsten > > -- > Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany > GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG > Nuernberg) > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > > -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From talatb at mellanox.com Mon Nov 13 08:47:59 2017 From: talatb at mellanox.com (Talat mellanox) Date: Mon, 13 Nov 2017 17:47:59 +0200 Subject: [sle-beta] yast2 system-clone is missing In-Reply-To: <20171112112008.GA5400@suse.de> References: <20171112081223.GA26059@suse.de> <20171112112008.GA5400@suse.de> Message-ID: When we generate the answer file we an internal error, attached screenshot. Will add the logs later On Sun, Nov 12, 2017 at 1:20 PM, Thorsten Kukuk wrote: > On Sun, Nov 12, Talat mellanox wrote: > > > it is already installed, > > ok i will try with BETA2 and update. > > autoyast2-installation is installed and yast2 clone_system does > not work? What is the error message? > Sure you didn't mix up with "autoyast2"? > > Thorsten > > > > > > > On Sun, Nov 12, 2017 at 10:12 AM, Thorsten Kukuk wrote: > > > > On Sun, Nov 12, Talat mellanox wrote: > > > > > So yast2 clone_system is missing, Any help ?? > > > > Yes, looks like you did not install it, so just install it ;) > > > > > Is this tool included in Beta? > > > > Yes, it is: > > zypper in autoyast2-installation > > > > Thorsten > > > > -- > > Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP > > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany > > GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG > > Nuernberg) > > _______________________________________________ > > sle-beta mailing list > > sle-beta at lists.suse.com > > http://lists.suse.com/mailman/listinfo/sle-beta > > > > > > -- > Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany > GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG > Nuernberg) > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: suseerror.png Type: image/png Size: 42326 bytes Desc: not available URL: From fcrozat at suse.com Mon Nov 13 09:09:49 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 13 Nov 2017 17:09:49 +0100 Subject: [sle-beta] yast2 system-clone is missing In-Reply-To: References: Message-ID: <1510589389.23811.15.camel@suse.com> Le dimanche 12 novembre 2017 ? 10:03 +0200, Talat mellanox a ?crit?: > > > On Fri, Nov 10, 2017 at 12:47 AM, David Kohler > wrote: > > I thought it was `yast2 clone_system`. > > > ? > Right, was my mistake. > So yast2 clone_system is missing, Any help ??? > Is this tool included in Beta? Try installing autoyast2 package. -- Frederic Crozat Enterprise Desktop Release Manager SUSE From fcrozat at suse.com Mon Nov 13 09:10:57 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 13 Nov 2017 17:10:57 +0100 Subject: [sle-beta] yast2 system-clone is missing In-Reply-To: References: <20171112081223.GA26059@suse.de> <20171112112008.GA5400@suse.de> Message-ID: <1510589457.23811.16.camel@suse.com> Le lundi 13 novembre 2017 ? 17:47 +0200, Talat mellanox a ?crit?: > When we generate the answer file we an internal error, attached > screenshot. > Will add the logs later Please open a bug report for this, with logs from save_y2logs commands. Thanks ! -- Frederic Crozat Enterprise Desktop Release Manager SUSE From vmoutoussamy at suse.com Mon Nov 13 09:59:36 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Mon, 13 Nov 2017 17:59:36 +0100 Subject: [sle-beta] Some questions about supported packages In-Reply-To: References: Message-ID: <2A86EEB6-0FDF-4E3B-86FC-EEEA8957E691@suse.com> Hi, Let?s have this discussion off the list. If other would like to have a discussion about SLE or any other SUSE Products subscriptions, please contact us via beta-programs at lists.suse.com *. Regards, *https://www.suse.com/betaprogram/sle-beta/#faq-private -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 13 Nov 2017, at 15:27, Sherry Crandall > wrote: > > I got the following question from a developer here. > > " Do we have an idea as to which of the modules will be covered via our SLES agreement? For the system management mission, we?re very much looking at needing things like container support (not necessarily the whole CAAS offering, but certainly the equivalent of the current Virtualization:containers repository) and other common components that are not currently in the base OS offering (including surprising omissions like RabbitMQ and support for the Go language and libraries)." > > Thanks, > Sherry > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From jrd at netlab1.net Mon Nov 13 10:08:50 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Mon, 13 Nov 2017 17:08:50 +0000 Subject: [sle-beta] Openssl v1.1.0-devel is absent In-Reply-To: <1510589389.23811.15.camel@suse.com> References: <1510589389.23811.15.camel@suse.com> Message-ID: ??? The documentation suggests that Openssl v1.1.0 is available. Indeed, library libopenssl1_1_0 is present. However, missing is the matching -devel material for it, with the latest such being for v1.0.2l. I mention this as I am in the middle of testing my code with versions of Openssl. I presume this is another loose end which will likely be cured in the next beta drop, or if you prefer I can add a bugzilla entry about it. ??? Thanks, ??? Joe D. From Dick.Waite at softwareag.com Mon Nov 13 10:17:47 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 13 Nov 2017 17:17:47 +0000 Subject: [sle-beta] Desktop Productivity Module Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010E92F11C@daeexmbx1.eur.ad.sag> Grand Evening. The Desktop Productivity Module shows a status of ?Not Registered? but there don't seem a way to register it. All the others show ?registered? __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Mon Nov 13 11:48:49 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 13 Nov 2017 18:48:49 +0000 Subject: [sle-beta] Timezone and NTP Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D010E92F1F7@daeexmbx1.eur.ad.sag> Grand Evening, One is asked at the beginning of an install with F2 what language to use... For me that is EN-UK later on in the install one gets a grand display of the world and we can say where "local" is, for many reasons I use Malta. At that point one can also configure which NTP server to use. So one is a little surprised when a number of UK NTP server are shown, none from the "local" area of Europe. Later on, with the system running one can see in /etc/systconfig /other / etc / sysconfig / clock / TIMEZONE and DEFAULT_TIMEZONE. One can see in TIMEZONE "Europe/Malta", looks grand, but in DEFAULT_TIMEZONE there is the value Europe/London. This seems to come from my choice of EN-UK, I would have thought "Europe/Malta" would have been the "DEFAULT_TIMEZONE" and "TIMEZONE" the value you set as one travels around. If one sets "DEFAULT_TIMEZONE" to Europe/Berlin you can then use a NTP server from Germany... I was looking for any NTP server giving a European time zone. Seems a bit arse-about-face, anyway NTP seems to be also on the blink... __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmarion at qualcomm.com Mon Nov 13 18:18:04 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Tue, 14 Nov 2017 01:18:04 +0000 Subject: [sle-beta] missing packages In-Reply-To: <20171107172359.GW7333@qualcomm.com> References: <20171107172359.GW7333@qualcomm.com> Message-ID: <20171114011801.GB30335@qualcomm.com> On Tue, Nov 07, 2017 at 09:23:59AM -0800, Mike Marion wrote: > Maybe I just missed it (pretty sure I dug around in all the ISOs) but > rpm-build is missing as well. I actually copied rpmbuild and the needed > libs from a 12.3 host, to build it from the rpm src.rpm. Fun. I see rpm-build is in Beta2 now, thanks. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From fcrozat at suse.com Tue Nov 14 02:09:20 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 14 Nov 2017 10:09:20 +0100 Subject: [sle-beta] Openssl v1.1.0-devel is absent In-Reply-To: References: <1510589389.23811.15.camel@suse.com> Message-ID: <1510650560.23811.22.camel@suse.com> Le lundi 13 novembre 2017 ? 17:08 +0000, Joe Doupnik a ?crit?: > ???? The documentation suggests that Openssl v1.1.0 is available.? > Indeed, library libopenssl1_1_0 is present. However, missing is the? > matching -devel material for it, with the latest such being for > v1.0.2l.? > I mention this as I am in the middle of testing my code with versions > of? > Openssl. I presume this is another loose end which will likely be > cured? > in the next beta drop, or if you prefer I can add a bugzilla entry > about it. Please create a bug report, this will ensure it is not forgotten. Thanks ! -- Frederic Crozat Enterprise Desktop Release Manager SUSE From fcrozat at suse.com Wed Nov 15 07:49:52 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Wed, 15 Nov 2017 15:49:52 +0100 Subject: [sle-beta] python-dmidecode no longer available in sles 15 beta 2? In-Reply-To: <024af714b0214215b2d9e6f7864c2846@sap.com> References: <024af714b0214215b2d9e6f7864c2846@sap.com> Message-ID: <1510757392.23811.29.camel@suse.com> Le mercredi 15 novembre 2017 ? 13:38 +0000, Bruggeman, Otto a ?crit?: > Hi, > ? > it appears python-dmidecode is no longer available in sles 15, it > this intentional? Please open a bug report with your use case, under the "Media content" component of SLES15. Thanks ! -- Frederic Crozat Enterprise Desktop Release Manager SUSE From otto.bruggeman at sap.com Wed Nov 15 09:18:33 2017 From: otto.bruggeman at sap.com (Bruggeman, Otto) Date: Wed, 15 Nov 2017 16:18:33 +0000 Subject: [sle-beta] python-dmidecode no longer available in sles 15 beta 2? In-Reply-To: <1510757392.23811.29.camel@suse.com> References: <024af714b0214215b2d9e6f7864c2846@sap.com> <1510757392.23811.29.camel@suse.com> Message-ID: <0fc82404e261467f81f86f2e7b28b596@sap.com> https://bugzilla.suse.com/show_bug.cgi?id=1068279 -----Original Message----- From: Frederic Crozat [mailto:fcrozat at suse.com] Sent: Mittwoch, 15. November 2017 15:50 To: Bruggeman, Otto (external - Partner) ; sle-beta at lists.suse.com Subject: Re: [sle-beta] python-dmidecode no longer available in sles 15 beta 2? Le mercredi 15 novembre 2017 ? 13:38 +0000, Bruggeman, Otto a ?crit?: > Hi, > ? > it appears python-dmidecode is no longer available in sles 15, it > this intentional? Please open a bug report with your use case, under the "Media content" component of SLES15. Thanks ! -- Frederic Crozat Enterprise Desktop Release Manager SUSE From mmarion at qualcomm.com Fri Nov 17 10:32:13 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Fri, 17 Nov 2017 17:32:13 +0000 Subject: [sle-beta] Anyone seeing issues with starting gnome-terminal? Message-ID: <20171117173212.GP13523@qualcomm.com> Before I open a bug, since it might be something I'm just missing.. is anyone seeing issues with starting things like gnome-terminal on a SLE15 B2 install? It reminds me of what I saw early on the 12.x betas, that ended up being locale stuff, but that doesn't seem to be it this time. Or the locale settings by default are odd. I can ssh -Y in, and start xterm fine. Try gnome-terminal and it times out with: sle15-beta2-vm(sles15) [~ (master)??]$ gnome-terminal Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached syslog shows: Nov 17 08:40:02 sle15-beta2-vm systemd[7512]: Started D-Bus User Message Bus. Nov 17 08:40:02 sle15-beta2-vm dbus-daemon[7576]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' Nov 17 08:40:02 sle15-beta2-vm systemd[7512]: Starting GNOME Terminal Server... Nov 17 08:40:02 sle15-beta2-vm gnome-terminal-server[7578]: Unable to init server: Could not connect: Connection refused Nov 17 08:40:02 sle15-beta2-vm gnome-terminal-server[7578]: Failed to parse arguments: Cannot open display: Nov 17 08:40:02 sle15-beta2-vm systemd[7512]: gnome-terminal-server.service: Main process exited, code=exited, status=10/n/a Nov 17 08:40:02 sle15-beta2-vm systemd[7512]: Failed to start GNOME Terminal Server. Nov 17 08:40:02 sle15-beta2-vm systemd[7512]: gnome-terminal-server.service: Unit entered failed state. Nov 17 08:40:02 sle15-beta2-vm systemd[7512]: gnome-terminal-server.service: Failed with result 'exit-code'. Nov 17 08:40:17 sle15-beta2-vm dbus-daemon[4532]: Failed to activate service 'org.gnome.Terminal': timed out I thought it might be something in my env, but even root simply gets: sle15-beta2-vm:~ # gnome-terminal systemd[7512]: Failed to start GNOME Terminal Server. Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached Google searches are all still returning basically the locale stuff that I've already dug into some, but it shows on this host: cornholio-kvm:~ # localectl System Locale: LANG=en_US.UTF-8 VC Keymap: us X11 Layout: n/a That does seem terse and the X11 layout is odd.. I didn't actually set/change anything related and it's the install defaults. I even checked both language settings and keyboard layout in yast to make sure something didn't just get missed. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From fcrozat at suse.com Mon Nov 20 09:32:12 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 20 Nov 2017 17:32:12 +0100 Subject: [sle-beta] Anyone seeing issues with starting gnome-terminal? In-Reply-To: <20171117173212.GP13523@qualcomm.com> References: <20171117173212.GP13523@qualcomm.com> Message-ID: <1511195532.23811.59.camel@suse.com> Le vendredi 17 novembre 2017 ? 17:32 +0000, Mike Marion a ?crit?: > Before I open a bug, since it might be something I'm just missing.. > is > anyone seeing issues with starting things like gnome-terminal on a > SLE15 > B2 install? > > It reminds me of what I saw early on the 12.x betas, that ended up > being > locale stuff, but that doesn't seem to be it this time.??Or the > locale > settings by default are odd. > > I can ssh -Y in, and start xterm fine.??Try gnome-terminal and it > times > out with: > sle15-beta2-vm(sles15) [~ (master)??]$ gnome-terminal > Error constructing proxy for > org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling > StartServiceByName for org.gnome.Terminal: Timeout was reached I'm not sure I fully understand your use-case. Are you trying to run gnome-terminal over ssh ?? -- Frederic Crozat Enterprise Desktop Release Manager SUSE From malcolmlewis at cableone.net Mon Nov 20 10:03:04 2017 From: malcolmlewis at cableone.net (Malcolm) Date: Mon, 20 Nov 2017 11:03:04 -0600 Subject: [sle-beta] [SLE15-Beta2] Support for amdgpu's Message-ID: <20171120110304.0242e13f@grover.homelinux.org> Hi Is the amdgpu driver going to appear in SLE 15, specifically CIK support for my R3 and R4/R5 Mullins cards? Or will I need to roll my own kmp? -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.92-18.36-default HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 up 6 days 14:24, 1 user, load average: 0.71, 0.62, 0.75 From mmarion at qualcomm.com Mon Nov 20 10:09:41 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Mon, 20 Nov 2017 17:09:41 +0000 Subject: [sle-beta] Anyone seeing issues with starting gnome-terminal? In-Reply-To: <1511195532.23811.59.camel@suse.com> References: <20171117173212.GP13523@qualcomm.com> <1511195532.23811.59.camel@suse.com> Message-ID: <20171120170940.GB7437@qualcomm.com> On Mon, Nov 20, 2017 at 05:32:12PM +0100, Frederic Crozat wrote: > I'm not sure I fully understand your use-case. > > Are you trying to run gnome-terminal over ssh ?? I was initially trying to run it in NX, but then yes, simply trying to start one over ssh fails. It's a VM without a GUI login locally, so I'm going to also test on bare metal to see if the same thing happens there when I get a chance. Perhaps it's simply related to the fact that there isn't an X11/Xorg running on the console at this point. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From donbuchholz.pdx at gmail.com Tue Nov 21 09:13:27 2017 From: donbuchholz.pdx at gmail.com (Don Buchholz) Date: Tue, 21 Nov 2017 08:13:27 -0800 Subject: [sle-beta] Problems with upgrade In-Reply-To: References: Message-ID: If you can see Grub menu, that means you should be able to edit the kernel boot params. Add "nomodeset" to them. That will probably keep your screen from going black. On Nov 21, 2017 6:52 AM, "Schulte, Matt" wrote: I have recently tried to upgrade from 12 SP3 to 15 Beta 2 and I notice two things: 1. My video seems to die sometime after selecting the new boot option in Grub. I get nothing but a black screen after that. I cannot switch to other terminals, no text, no gui?nothing. I know the server is booted because I can still SSH into it, which leads me to my next issue. 2. I had created a root user and nothing else (hey, I?m only testing!) on 12 SP3 and now I can no longer log in. Either my password has changed or some sshd policy disallowing ssh as root has been enabled. Either way I?m dead in the water, can get to a console either way. Anybody tried to upgrade so far? I was hoping this would let me get past the installation issues. _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From fcrozat at suse.com Tue Nov 21 09:24:15 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 21 Nov 2017 17:24:15 +0100 Subject: [sle-beta] Anyone seeing issues with starting gnome-terminal? In-Reply-To: <20171120170940.GB7437@qualcomm.com> References: <20171117173212.GP13523@qualcomm.com> <1511195532.23811.59.camel@suse.com> <20171120170940.GB7437@qualcomm.com> Message-ID: <1511281455.31551.3.camel@suse.com> Le lundi 20 novembre 2017 ? 17:09 +0000, Mike Marion a ?crit?: > On Mon, Nov 20, 2017 at 05:32:12PM +0100, Frederic Crozat wrote: > > > > > I'm not sure I fully understand your use-case. > > > > Are you trying to run gnome-terminal over ssh ?? > > I was initially trying to run it in NX, but then yes, simply trying > to > start one over ssh fails.??It's a VM without a GUI login locally, so > I'm > going to also test on bare metal to see if the same thing happens > there > when I get a chance.??Perhaps it's simply related to the fact that > there > isn't an X11/Xorg running on the console at this point. I think it related to the fact GNOME Terminal (and many GNOME applications) are designed to connect to a D-Bus session, which isn't running if you are using ssh / NX or might be terminated at some point. And to be honest, I fail to see the value of running xterm / gnome- terminal over SSH: you'll get high latency. It might be better to run your commands directly over ssh or use full desktop remote desktop session, like VNC or RDP (which will better handle compression). -- Frederic Crozat Enterprise Desktop Release Manager SUSE From fcrozat at suse.com Tue Nov 21 09:28:52 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 21 Nov 2017 17:28:52 +0100 Subject: [sle-beta] [SLE15-Beta2] Support for amdgpu's In-Reply-To: <20171120110304.0242e13f@grover.homelinux.org> References: <20171120110304.0242e13f@grover.homelinux.org> Message-ID: <1511281732.31551.4.camel@suse.com> Le lundi 20 novembre 2017 ? 11:03 -0600, Malcolm a ?crit?: > Hi > Is the amdgpu driver going to appear in SLE 15, specifically CIK > support for my R3 and R4/R5 Mullins cards? > > Or will I need to roll my own kmp? I don't have a answer for it, but you could open a bug report, just to make sure we track this appropriately. Thanks ! -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Matt.Schulte at netapp.com Tue Nov 21 13:56:14 2017 From: Matt.Schulte at netapp.com (Schulte, Matt) Date: Tue, 21 Nov 2017 20:56:14 +0000 Subject: [sle-beta] Problems with upgrade In-Reply-To: References: Message-ID: > If you can see Grub menu, that means you should be able to edit the kernel boot params. Add "nomodeset" to them. That will probably keep your screen from going black. Ok, nomodeset got my video working again. Now I?m left with number 2, it would seem that I am no longer allowed to log in as my root user. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmarion at qualcomm.com Tue Nov 21 15:26:36 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Tue, 21 Nov 2017 22:26:36 +0000 Subject: [sle-beta] Anyone seeing issues with starting gnome-terminal? In-Reply-To: <1511281455.31551.3.camel@suse.com> References: <20171117173212.GP13523@qualcomm.com> <1511195532.23811.59.camel@suse.com> <20171120170940.GB7437@qualcomm.com> <1511281455.31551.3.camel@suse.com> Message-ID: <20171121222633.GA5581@qualcomm.com> On Tue, Nov 21, 2017 at 05:24:15PM +0100, Frederic Crozat wrote: > I think it related to the fact GNOME Terminal (and many GNOME > applications) are designed to connect to a D-Bus session, which isn't > running if you are using ssh / NX or might be terminated at some point. It should try to start up dbus though, and it works/worked on SLE <15. > And to be honest, I fail to see the value of running xterm / gnome- > terminal over SSH: you'll get high latency. It might be better to run > your commands directly over ssh or use full desktop remote desktop > session, like VNC or RDP (which will better handle compression). Oh I know, it's just that it's something that has always worked before. I was actually trying to simply run it inside of an NX session initally as well. LOL.. I just tried something.. I started a vncserver on the SLE15 host, connected... gnome works. NOW I can start another gnome-terminal via ssh or NX as well. I've seen a similar odd thing on 12.3 as well where if I start a remote NX session first, I can't login to gnome on the console without killing the NX session first. I think I'm getting hit by gnome-dev "I never use it that way" decisions. I tested by rebooting the VM: $ gnome-terminal Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached $ vncserver New 'susetest-kvm:1 ($ME)' desktop is susetest-kvm:1 Starting applications specified in /usr2/$ME/.vnc/xstartup Log file is /usr2/$ME/.vnc/susetest-kvm:1.log [snip] Connected and couldn't open gnome-terminal via gnome buttons this time, but starting xterm and running it inside the vnc session worked, now, via ssh gnome-terminal works again. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From malcolmlewis at cableone.net Tue Nov 21 17:24:33 2017 From: malcolmlewis at cableone.net (Malcolm) Date: Tue, 21 Nov 2017 18:24:33 -0600 Subject: [sle-beta] [SLE15-Beta2] Support for amdgpu's In-Reply-To: <1511281732.31551.4.camel@suse.com> References: <20171120110304.0242e13f@grover.homelinux.org> <1511281732.31551.4.camel@suse.com> Message-ID: <20171121182433.1359f5aa@grover.homelinux.org> On Tue, 21 Nov 2017 17:28:52 +0100 Frederic Crozat wrote: > Le lundi 20 novembre 2017 ? 11:03 -0600, Malcolm a ?crit?: > > Hi > > Is the amdgpu driver going to appear in SLE 15, specifically CIK > > support for my R3 and R4/R5 Mullins cards? > > > > Or will I need to roll my own kmp? > > I don't have a answer for it, but you could open a bug report, just to > make sure we track this appropriately. > > Thanks ! > Hi Done: https://bugzilla.suse.com/show_bug.cgi?id=1069343 -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.92-18.36-default HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 up 7 days 21:49, 1 user, load average: 0.70, 1.53, 1.17 From fcrozat at suse.com Wed Nov 22 01:52:01 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Wed, 22 Nov 2017 09:52:01 +0100 Subject: [sle-beta] Anyone seeing issues with starting gnome-terminal? In-Reply-To: <20171121222633.GA5581@qualcomm.com> References: <20171117173212.GP13523@qualcomm.com> <1511195532.23811.59.camel@suse.com> <20171120170940.GB7437@qualcomm.com> <1511281455.31551.3.camel@suse.com> <20171121222633.GA5581@qualcomm.com> Message-ID: <1511340721.31551.6.camel@suse.com> Le mardi 21 novembre 2017 ? 22:26 +0000, Mike Marion a ?crit?: > On Tue, Nov 21, 2017 at 05:24:15PM +0100, Frederic Crozat wrote: > > > > > I think it related to the fact GNOME Terminal (and many GNOME > > applications) are designed to connect to a D-Bus session, which > > isn't > > running if you are using ssh / NX or might be terminated at some > > point. > > It should try to start up dbus though, and it works/worked on SLE > <15. gnome-terminal has changed since SLE12 to use a "factory" process to handle the various terminal creation, this is probably the reason you have this issue. > > > > > And to be honest, I fail to see the value of running xterm / gnome- > > terminal over SSH: you'll get high latency. It might be better to > > run > > your commands directly over ssh or use full desktop remote desktop > > session, like VNC or RDP (which will better handle compression). > > Oh I know, it's just that it's something that has always worked > before. > I was actually trying to simply run it inside of an NX session > initally > as well.?? > > LOL.. I just tried something.. I started a vncserver on the SLE15 > host, > connected... gnome works.??NOW I can start another gnome-terminal via > ssh or NX as well.??I've seen a similar odd thing on 12.3 as well > where > if I start a remote NX session first, I can't login to gnome on the > console without killing the NX session first. This is expected: only one graphical session for a single user is allowed at the same time. This is why are shipping a VNC multiplexer to handle this kind of issue ;) -- Frederic Crozat Enterprise Desktop Release Manager SUSE From kukuk at suse.de Wed Nov 22 05:05:58 2017 From: kukuk at suse.de (Thorsten Kukuk) Date: Wed, 22 Nov 2017 13:05:58 +0100 Subject: [sle-beta] Who is using SLP (Service Location Protocol)? Message-ID: <20171122120558.GA25871@suse.de> Hi, since we had a discussion currently about how reliable SLP is, I would like to take the chance and ask you as our Beta testers, who is using SLP in their network? And for what are you using it? For this who don't know what SLP is: Service Location Protocol https://en.wikipedia.org/wiki/Service_Location_Protocol Thank you, Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From thomas.kronseder at mtu.de Wed Nov 22 05:17:13 2017 From: thomas.kronseder at mtu.de (KRONSEDER, Thomas, Dr.) Date: Wed, 22 Nov 2017 12:17:13 +0000 Subject: [sle-beta] Who is using SLP (Service Location Protocol)? In-Reply-To: <20171122120558.GA25871@suse.de> References: <20171122120558.GA25871@suse.de> Message-ID: <01559031EB071C47AA06542D982B9CD5A1F2D378@memc023.de.mtu.corp> Hi, in my case it's the other way round: We're trying to cut down any type of broadcast or auto-negotiation traffic to the very needed. In large networks such type of traffic is a source of trouble, and in case of strict operation rules in place auto-negotiation is actually counterproductive. Best regards, Thomas -----Urspr?ngliche Nachricht----- Von: sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces at lists.suse.com] Im Auftrag von Thorsten Kukuk Gesendet: Mittwoch, 22. November 2017 13:06 An: sle-beta at lists.suse.com Betreff: [sle-beta] Who is using SLP (Service Location Protocol)? Hi, since we had a discussion currently about how reliable SLP is, I would like to take the chance and ask you as our Beta testers, who is using SLP in their network? And for what are you using it? For this who don't know what SLP is: Service Location Protocol https://en.wikipedia.org/wiki/Service_Location_Protocol Thank you, Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta -- MTU Aero Engines AG Vorstand/Board of Management: Reiner Winkler, Vorsitzender/CEO; Dr. Rainer Martens, Michael Schreyoegg Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Klaus Eberhardt Sitz der Gesellschaft/Registered Office: Muenchen Handelsregister/Commercial Register: Muenchen HRB 157206 Diese E-Mail sowie ihre Anhaenge enthalten MTU-eigene vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte den Absender und loeschen Sie diese E-Mail sowie die Anhaenge. Das unbefugte Speichern, Kopieren oder Weiterleiten ist nicht gestattet. This e-mail and any attached documents are proprietary to MTU, confidential or protected by law. If you are not the intended recipient, please advise the sender and delete this message and its attachments. Any unauthorised storing, copying or distribution is prohibited. From rbrown at suse.de Wed Nov 22 05:29:59 2017 From: rbrown at suse.de (Richard Brown) Date: Wed, 22 Nov 2017 13:29:59 +0100 Subject: [sle-beta] Who is using SLP (Service Location Protocol)? In-Reply-To: <20171122120558.GA25871@suse.de> References: <20171122120558.GA25871@suse.de> Message-ID: <1511353799.13713.12.camel@suse.de> On Wed, 2017-11-22 at 13:05 +0100, Thorsten Kukuk wrote: > Hi, > > since we had a discussion currently about how reliable SLP is, I would > like to take the chance and ask you as our Beta testers, who is using > SLP in their network? > And for what are you using it? > > For this who don't know what SLP is: Service Location Protocol > https://en.wikipedia.org/wiki/Service_Location_Protocol > > Thank you, > Thorsten The only time I ever came across SLP in my former life as a sysadmin was as a result of Novell OES It is/was (haven't looked at it in 4 years) used quite heavily there for service discovery for many of the Novell services, especially eDirectory, where is it used to find the IP addresses of the servers in the replica ring. SLP issues would therefore cause eDirectory sync issues, which would have dramatic problems for basic functionality such as authentication. Tuning SLP to avoid this was a chore that had to be repeated as networks grew in size and complexity. HTH -- Richard Brown Linux Distribution Engineer - Future Technology Team Chairman - openSUSE Phone +4991174053-361 SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From jrd at netlab1.net Wed Nov 22 06:17:30 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Wed, 22 Nov 2017 13:17:30 +0000 Subject: [sle-beta] Who is using SLP (Service Location Protocol)? In-Reply-To: <20171122120558.GA25871@suse.de> References: <20171122120558.GA25871@suse.de> Message-ID: <229c39e2-3b00-7dc4-9154-792a53ecb098@netlab1.net> On 22/11/2017 12:05, Thorsten Kukuk wrote: > Hi, > > since we had a discussion currently about how reliable SLP is, I would > like to take the chance and ask you as our Beta testers, who is using > SLP in their network? > And for what are you using it? > > For this who don't know what SLP is: Service Location Protocol > https://en.wikipedia.org/wiki/Service_Location_Protocol > > Thank you, > Thorsten --------------- ??? My systems use it, for the same reason as given by Richard: to support eDirectory and such on OES systems. ??? A long time ago one of my grad students did her MS on improving SLP by using DNS as a better pointer mechanism. Alas, the powers that be decided to stick with the awkward approach which we still have today. It's too bad that Google did not chime in with "we know where things hide, just ask the search box." ??? So, it is a required mechanism on the machines which I oversee, not to mention others also emanating from Provo. ??? Thanks, ??? Joe D. From alexander.hass at sap.com Wed Nov 22 09:24:05 2017 From: alexander.hass at sap.com (Alexander Hass) Date: Wed, 22 Nov 2017 17:24:05 +0100 Subject: [sle-beta] How to completely display pattern contents? Message-ID: Hi All, I am wondering how to completely display the contents of a pattern. On SLE 12 for example 'zypper pattern-info base' used to display all dependent packages, where SLE 15 does ony list the included 'meta' packages: # zypper pattern-info base Refreshing service 'SMT-http_x'. Loading repository data... Reading installed packages... Information for pattern base: ----------------------------- Repository : SLE-Module-Basesystem15-Pool Name : base Version : 20170319-9.1 Arch : x86_64 Vendor : SUSE LLC Installed : Yes Visible to User : Yes Summary : Base System Description : This is the base runtime system. It contains only a minimal multiuser booting system. For running on real hardware, you need to add additional packages and pattern to make this pattern useful on its own. Contents : S | Name | Type | Dependency ---+----------------------------------+---------+------------ i | kbd | package | Required i+ | openssh | package | Required i+ | patterns-base-base | package | Required i | patterns-base-minimal_base | package | Required | patterns-base-minimal_base-32bit | package | Required i | polkit | package | Required i | polkit-default-privs | package | Required i | rpm | package | Required i | shadow | package | Required i | util-linux | package | Required i | which | package | Required i | branding-SLE | package | Recommended i | ca-certificates-mozilla | package | Recommended i+ | grub2 | package | Recommended i | grub2-x86_64-efi | package | Recommended i | shim | package | Recommended i | systemd-sysvinit | package | Recommended So how to display the full list - or how to at least resolve the packages pulled by the 'meta' package like 'patterns-base-base' for example? Thank you, Alexander. From kukuk at suse.de Wed Nov 22 10:34:03 2017 From: kukuk at suse.de (Thorsten Kukuk) Date: Wed, 22 Nov 2017 18:34:03 +0100 Subject: [sle-beta] How to completely display pattern contents? In-Reply-To: References: Message-ID: <20171122173403.GA28369@suse.de> Hi, On Wed, Nov 22, Alexander Hass wrote: > Hi All, > > I am wondering how to completely display the contents of a pattern. > On SLE 12 for example 'zypper pattern-info base' used to display all > dependent packages, where SLE 15 does ony list the included 'meta' packages: It works the same way, as you can see on the output of "zypper pattern-info base": shadow, rpm, util-linux, ... > So how to display the full list - or how to at least resolve the packages pulled > by the 'meta' package like 'patterns-base-base' for example? I have to admit, the patterns implementation is not really easy to understand. The RPM package "patterns-base-base" is the pattern "base". So "zypper pattern-info base" shows you the informations about the pattern "base" provided by the RPM "patterns-base-base". That you see see RPM "patterns-base-base" in the required list of the pattern "base" is, because the pattern needs this RPM which provides itself as pattern. I know that's very confusing and leads quite often to problems, if people do different things to the pattern and RPM at the same time. The pattern provided by patterns-base-minimal_base can now be displayed with "zypper pattern-info minimal_base". But, there is a much easier solution: "zypper info --requires --recommends patterns-base-base" And now you have to go recursive through the list: "zypper info --requires --recommends patterns-base-base patterns-base-minimal_base" This is not really different from SLE12. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From mjambor at suse.cz Thu Nov 23 03:29:11 2017 From: mjambor at suse.cz (Martin Jambor) Date: Thu, 23 Nov 2017 11:29:11 +0100 Subject: [sle-beta] Beta 3 ? In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F03D1@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F03D1@daeexmbx1.eur.ad.sag> Message-ID: Hi, On Thu, Nov 23 2017, Dick Waite wrote: > Grand New Thanksgiving Day, > > Will we see Beta 3 today ? > Planned Releases > > Our plan is to release 5 Betas, 3 Release Candidates and one GMC from 27th October 2017 to 19th April 2018. > > Scheduled releases: > > * Beta 1 ? 27-10-2017 > * Beta 2 ? 09-11-2017 > * Beta 3 ? 22-11-2017 > * Beta 4 ? 07-12-2017 > * Beta 5 ? 18-01-2018 > > more dates to be announced Yesterday Kai linked a slide-deck with schedule info for partners to the PM page on our wiki: https://wiki.microfocus.net/images/e/ee/SUSE_Linux_Enterprise_15_schedule.pdf In addition to the above, It has Beta6 scheduled on 2018-02-01 and Beta7 on 2018-02-15. And of it is apparently ready to be directly sent to our NDA partners. For reference, the PM page I'm speaking about is https://wiki.microfocus.net/index.php?title=SUSE/Product_Management (I set wiki to send me notifications of changes, that's how I know.) There is also a new SLE 15 roadmap slide-deck but I did not go through it. HTH, Martin From Dick.Waite at softwareag.com Thu Nov 23 04:54:20 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Thu, 23 Nov 2017 11:54:20 +0000 Subject: [sle-beta] Beta 3 ? In-Reply-To: References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F03D1@daeexmbx1.eur.ad.sag>, Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F6F058F@daeexmbx1.eur.ad.sag> Many Thanks Martin, Grand to see some SUSE people are not on a"Thanksgiving" holiday ;o) I did try to access your links but to both I got: "The user name is not valid or is not eligible to use this feature" I do have a userid/password to access the Beta but not these url's.. So from what you say, yesterday was still a good day for Beta3, quite pleased about that 'cos it would be a little impolite not to let the many volunteers who are Beta testing SUSE code at no cost that they could use the time for their own use. Many Thanks for the dates of the two extra Betas. Question if I may, do you know which Beta will allow the use of "Update" and or "Migrate" our machines from SLES12 to SLES15 ? I have ran a number of new installs and given feed back, but it's getting my SLES12 machines onto SLES15 that is the big point for the company. and ... is there any Docu on how this "Update" "Migrate" is to be run, the words we have at the moment say there will be an update "in due course", which does suggest they way we did do it for SLES12 is not going to be the way with SLES15. Again many thanks for the very good words and I'll try and get a working user/pass to access the urls posted. __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Martin Jambor [mjambor at suse.cz] Sent: 23 November 2017 11:29 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] Beta 3 ? Hi, On Thu, Nov 23 2017, Dick Waite wrote: > Grand New Thanksgiving Day, > > Will we see Beta 3 today ? > Planned Releases > > Our plan is to release 5 Betas, 3 Release Candidates and one GMC from 27th October 2017 to 19th April 2018. > > Scheduled releases: > > * Beta 1 ? 27-10-2017 > * Beta 2 ? 09-11-2017 > * Beta 3 ? 22-11-2017 > * Beta 4 ? 07-12-2017 > * Beta 5 ? 18-01-2018 > > more dates to be announced Yesterday Kai linked a slide-deck with schedule info for partners to the PM page on our wiki: https://wiki.microfocus.net/images/e/ee/SUSE_Linux_Enterprise_15_schedule.pdf In addition to the above, It has Beta6 scheduled on 2018-02-01 and Beta7 on 2018-02-15. And of it is apparently ready to be directly sent to our NDA partners. For reference, the PM page I'm speaking about is https://wiki.microfocus.net/index.php?title=SUSE/Product_Management (I set wiki to send me notifications of changes, that's how I know.) There is also a new SLE 15 roadmap slide-deck but I did not go through it. HTH, Martin _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From vmoutoussamy at suse.com Thu Nov 23 05:31:44 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 23 Nov 2017 13:31:44 +0100 Subject: [sle-beta] Beta 3 ? In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F03D1@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F03D1@daeexmbx1.eur.ad.sag> Message-ID: <40DDD580-29B8-4AA7-98FD-ED96FE73E190@suse.com> Hi, Thank you for your patience, we are still in the last QA steps for beta3. So we do not expect a release until Friday. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 23 Nov 2017, at 09:26, Waite, Dick (External) wrote: > > Grand New Thanksgiving Day, > > Will we see Beta 3 today ? > Planned Releases > > Our plan is to release 5 Betas, 3 Release Candidates and one GMC from 27th October 2017 to 19th April 2018. > Scheduled releases: > Beta 1 ? 27-10-2017 > Beta 2 ? 09-11-2017 > Beta 3 ? 22-11-2017 > Beta 4 ? 07-12-2017 > Beta 5 ? 18-01-2018 > more dates to be announced > > __R > > Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From vmoutoussamy at suse.com Thu Nov 23 06:00:01 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 23 Nov 2017 14:00:01 +0100 Subject: [sle-beta] Beta 3 ? In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F058F@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F03D1@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F058F@daeexmbx1.eur.ad.sag> Message-ID: <541F43C6-9D69-47B2-82C5-A04592B601A2@suse.com> Hi, > On 23 Nov 2017, at 12:54, Waite, Dick (External) wrote: > > Many Thanks Martin, > > Grand to see some SUSE people are not on a"Thanksgiving" holiday ;o) > > I did try to access your links but to both I got: > > "The user name is not valid or is not eligible to use this feature" > > I do have a userid/password to access the Beta but not these url's.. That?s normal, these are internal SUSE links and they won?t be accessible. > So from what you say, yesterday was still a good day for Beta3, quite pleased about that 'cos it would be a little impolite not to let the many volunteers who are Beta testing SUSE code at no cost that they could use the time for their own use. > > Many Thanks for the dates of the two extra Betas. Well, keep in mind that the public beta release dates are prone to some changes depending on various technical reasons (Build, QA, Bugs, CDN, etc?). We are trying to do our best but the quality of what we provide is more important than releasing on time for the beta. And we are aware that any delay or slip will affect beta testers but it also affect us internally. So we are not taking this slightly! > Question if I may, do you know which Beta will allow the use of "Update" and or "Migrate" our machines from SLES12 to SLES15 ? I have ran a number of new installs and given feed back, but it's getting my SLES12 machines onto SLES15 that is the big point for the company. Offline migration should work with beta3, Online migration still require more work. More information will come on this topic! > and ... is there any Docu on how this "Update" "Migrate" is to be run, the words we have at the moment say there will be an update "in due course", which does suggest they way we did do it for SLES12 is not going to be the way with SLES15. Yes, but still a work in progress. For now we are only providing the quick installation guide for SLES and SLED[*],but I would really like to provide more in the near future. > > Again many thanks for the very good words and I'll try and get a working user/pass to access the urls posted. > > __R Thanks for your enthusiasm, hopefully all of your questions will be addressed soon. Regards, [*] https://www.suse.com/betaprogram/sle-beta/#documentation -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From beta-programs at lists.suse.com Fri Nov 24 09:37:42 2017 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Fri, 24 Nov 2017 17:37:42 +0100 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! Message-ID: <5a184ad6a143f_1a025dd3247222a@boucane.mail> Here comes Beta 3 of SUSE Linux Enterprise 15: SUSE Linux Enterprise Server (SLES), SUSE Linux Enterprise Desktop (SLED), SUSE Linux Enterprise High Availability (SLE-HA), and SUSE Linux Enterprise Workstation Extension (SLE-WE) Download[1] == Important =Online Channels for Beta 3: At the time of this announcement, our SCC online channels synchronisations are still in progress. We expect them to finish in a few hours, in the mean time you need to use the "Installer" and "Packages" isos for your testing. =Migration from SLE 12 to SLE 15: With Beta 3, we are still not in an ideal state for the support of the different Migration scenarios from SLE 12 to SLE 15. You can try it but it is not expected to be smooth! Nevertheless do not hesitate to share your findings if you face any issues, but keep in mind that we are working on it. - Offline migration: With Beta 3, it is possible by using the "Installer" and "Packages" isos. - Online migration: Not possible with Beta 3, the SCC setup of the online channels still needs adaptation. We hope to get this done for future beta releases. == More information SLE Beta Page[2] Release Notes[3] Known Issues[4] Your SUSE Linux Enterprise Team == Beta Program Please refer to our dedicated SLE Beta Program webpage[1] for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1] https://www.suse.com/betaprogram/sle-beta/#download [2] https://www.suse.com/betaprogram/sle-beta [3] https://www.suse.com/betaprogram/sle-beta/#releasenotes [4] https://www.suse.com/betaprogram/sle-beta/#knownissues -------------- next part -------------- An HTML attachment was scrubbed... URL: From malcolmlewis at cableone.net Fri Nov 24 10:02:35 2017 From: malcolmlewis at cableone.net (Malcolm) Date: Fri, 24 Nov 2017 11:02:35 -0600 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <5a184ad6a143f_1a025dd3247222a@boucane.mail> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> Message-ID: <20171124110235.68cdf342@grover.homelinux.org> On Fri, 24 Nov 2017 17:37:42 +0100 SUSE Beta Program wrote: > Here comes Beta 3 of SUSE Linux Enterprise 15: > SUSE Linux Enterprise Server (SLES), > SUSE Linux Enterprise Desktop (SLED), > SUSE Linux Enterprise High Availability (SLE-HA), > and SUSE Linux Enterprise Workstation Extension (SLE-WE) > Hi Can some kind person update the checksums.. specifically SHA256SUMS for Beta 3. -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.92-18.36-default HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 up 10 days 14:25, 1 user, load average: 2.79, 2.32, 1.30 From vmoutoussamy at suse.com Fri Nov 24 11:47:52 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Fri, 24 Nov 2017 19:47:52 +0100 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <20171124110235.68cdf342@grover.homelinux.org> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> Message-ID: Hi, > On 24 Nov 2017, at 18:02, Malcolm > wrote: > > On Fri, 24 Nov 2017 17:37:42 +0100 > SUSE Beta Program > wrote: > >> Here comes Beta 3 of SUSE Linux Enterprise 15: >> SUSE Linux Enterprise Server (SLES), >> SUSE Linux Enterprise Desktop (SLED), >> SUSE Linux Enterprise High Availability (SLE-HA), >> and SUSE Linux Enterprise Workstation Extension (SLE-WE) >> > Hi > Can some kind person update the checksums.. specifically SHA256SUMS for > Beta 3. What?s wrong with it? Maybe our browser cache or our CDN is playing some tricks. I have the following content in the SHA256SUMS: 6e6d098ddce5398d422679ae1a4aa8b69a04b37387e2d82f2a3238f68ff90b34 SLE-15-Installer-DVD-aarch64-Beta3-DVD1.iso 34c1e915c8cceb1e69e22f51f48a4ffd8deab4a345d971a0c569491af18d9c69 SLE-15-Installer-DVD-aarch64-Beta3-DVD2.iso 8ff435b2ed39c41816d4369a97bf541e027096ddb627af1ab8da9097e3acdeaf SLE-15-Installer-DVD-aarch64-Beta3-DVD3.iso 8583c56e3f2ac46ae664cb6d0906ffb362c2dafc8c2564306f322c7a1f3f7992 SLE-15-Installer-DVD-ppc64le-Beta3-DVD1.iso 88d78ebb58abe054dc05011c8a39293cd36f7cb5957bc4d37c923ace60514aa5 SLE-15-Installer-DVD-ppc64le-Beta3-DVD2.iso e12c51cba623b89e6c573abf355e0a13f6b9b0a07089d6d67f7626b83164fa0f SLE-15-Installer-DVD-ppc64le-Beta3-DVD3.iso c6618550d16f337582c4ca667147534405f8a957e32db46bb8e3c9b0fa4aeaa3 SLE-15-Installer-DVD-s390x-Beta3-DVD1.iso 2d0781763fffff1a2a8e980f1c5a0ff527ac5e5ced36d37ac115ea00ef961c33 SLE-15-Installer-DVD-s390x-Beta3-DVD2.iso 9af1fc94c65c7bed8e7b7b111b7a3392943c26a7acbd0967792551e39ce3a3d5 SLE-15-Installer-DVD-s390x-Beta3-DVD3.iso b369876ce17823857dc3fd5d812d304dc419b3769990082226aa3cfd5a611954 SLE-15-Installer-DVD-x86_64-Beta3-DVD1.iso 5ae31a2ed358ec8d2c7fab1e8c511ee386a8a18f6068ad7dd946c7ca80861dbc SLE-15-Installer-DVD-x86_64-Beta3-DVD3.iso c3ea69206ad649ff1f227eab591bb0f3517d60d1ea7e1d23e3922e7158124292 SLE-15-Packages-aarch64-Beta3-DVD1.iso f274f3f7b3007ab032d44984ddfa1e38399d6f67fed802695fa4a02814a9c2b5 SLE-15-Packages-aarch64-Beta3-DVD2.iso c63423a3ff431ed765d1098cdddd6daa46912da12744df445f986ce9ada8fb1d SLE-15-Packages-aarch64-Beta3-DVD3.iso 365f971c70d1fd5ef02a5decbe8f83dd7bffeaedf5c9398831b391d61936437d SLE-15-Packages-ppc64le-Beta3-DVD1.iso 7652c94bc1671a4600f11f004f9576a03f896799b42615a9d0ffa067b05f86ae SLE-15-Packages-ppc64le-Beta3-DVD2.iso a959d5536b8db0aebf4be5beb4e352cf22f11142e0b81648e3e298598c20c931 SLE-15-Packages-ppc64le-Beta3-DVD3.iso b7ac0303c194629321784e022ccee735e72cb8eacea99bb1db0dd74ae00d1954 SLE-15-Packages-s390x-Beta3-DVD1.iso ac4a4a3e526bd699e292ad69feecacf38e5ac7d2bc9a16c132c16a4cd062aff6 SLE-15-Packages-s390x-Beta3-DVD2.iso ad31fac7b6f975e9ef736bbcc679a092d08d8fde8e7f0039dbac5c3c44bef5f0 SLE-15-Packages-s390x-Beta3-DVD3.iso b115b40e9731eaa44a77802d104a78e5ab9e70bc0e84d6442c6b1a7a2a69eee0 SLE-15-Packages-x86_64-Beta3-DVD1.iso ae0ffe8181e4bcfd18bd092d06dca1ff9b2c4555c8a7d0f3efcb645f1c937bd9 SLE-15-Packages-x86_64-Beta3-DVD2.iso 527f733587b2f26ebda62a527c45309aa9958e8b039f3785548d7b67a47d16ad SLE-15-Packages-x86_64-Beta3-DVD3.iso -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > -- > Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) > openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.92-18.36-default > HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 > up 10 days 14:25, 1 user, load average: 2.79, 2.32, 1.30 > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From Dick.Waite at softwareag.com Fri Nov 24 17:55:01 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Sat, 25 Nov 2017 00:55:01 +0000 Subject: [sle-beta] Upgrade Beta3 Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> Grand Night, A new install ran Okay. I tried an offline migration using the installer and package: Finds the old version Okay then pops off to the SCC and you then get a "No migration product found". I tried with out a network and then I get an internal error. Need to stop it asking home about an update.... Migration from SLE 12 to SLE 15 With Beta 3, we are still not in an ideal state for the support of the different migration scenarios from SLE 12 to SLE 15. You can try it but it is not expected to be smooth! Nevertheless do not hesitate to share your findings if you face any issues, but keep in mind that we are working on it. * Offline migration: With Beta 3, it is possible by using the SLE-15-Installer and SLE-15-Packages isos. __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Fri Nov 24 18:33:42 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Sat, 25 Nov 2017 01:33:42 +0000 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> I had a glass of Irish... SUSEConnect --cleanup to remove all registration trace. shutdown -r now upgrade as the words say, it's a big bumpy but along this track you do get into upgrade mode... Seems if the system knows it's registered it pop's off home... More in the morning, I'll let this update tonight. __R ________________________________ From: Waite, Dick (External) Sent: 25 November 2017 01:55 To: 'sle-beta at lists.suse.com' Cc: 'Vincent Moutoussamy' Subject: Upgrade Beta3 Grand Night, A new install ran Okay. I tried an offline migration using the installer and package: Finds the old version Okay then pops off to the SCC and you then get a "No migration product found". I tried with out a network and then I get an internal error. Need to stop it asking home about an update.... Migration from SLE 12 to SLE 15 With Beta 3, we are still not in an ideal state for the support of the different migration scenarios from SLE 12 to SLE 15. You can try it but it is not expected to be smooth! Nevertheless do not hesitate to share your findings if you face any issues, but keep in mind that we are working on it. * Offline migration: With Beta 3, it is possible by using the SLE-15-Installer and SLE-15-Packages isos. __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Fri Nov 24 23:01:54 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Sat, 25 Nov 2017 06:01:54 +0000 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag>, <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F6F14BF@daeexmbx1.eur.ad.sag> All seems well bar the "SUSE Linux Enterprise Development Kit 12 SP3" which is in RED and says it will be removed, but it's marked as an error and it's stopping the ball rolling. Anyway time to go to the day job, sort out some issues with Windows 10 RS4 ;o) Have you all a very grand day. __R ________________________________ From: Waite, Dick (External) Sent: 25 November 2017 02:33 To: 'sle-beta at lists.suse.com' Cc: 'Vincent Moutoussamy' Subject: RE: Upgrade Beta3 I had a glass of Irish... SUSEConnect --cleanup to remove all registration trace. shutdown -r now upgrade as the words say, it's a big bumpy but along this track you do get into upgrade mode... Seems if the system knows it's registered it pop's off home... More in the morning, I'll let this update tonight. __R ________________________________ From: Waite, Dick (External) Sent: 25 November 2017 01:55 To: 'sle-beta at lists.suse.com' Cc: 'Vincent Moutoussamy' Subject: Upgrade Beta3 Grand Night, A new install ran Okay. I tried an offline migration using the installer and package: Finds the old version Okay then pops off to the SCC and you then get a "No migration product found". I tried with out a network and then I get an internal error. Need to stop it asking home about an update.... Migration from SLE 12 to SLE 15 With Beta 3, we are still not in an ideal state for the support of the different migration scenarios from SLE 12 to SLE 15. You can try it but it is not expected to be smooth! Nevertheless do not hesitate to share your findings if you face any issues, but keep in mind that we are working on it. * Offline migration: With Beta 3, it is possible by using the SLE-15-Installer and SLE-15-Packages isos. __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dick.Waite at softwareag.com Fri Nov 24 23:38:35 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Sat, 25 Nov 2017 06:38:35 +0000 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F14BF@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag>, <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag>, <46AC8C81C10B8C48820201DF2AE1D76D011F6F14BF@daeexmbx1.eur.ad.sag> Message-ID: <20171125063834.5644375.4219.31039@softwareag.com> Also how do you get the Workstation Extension into the ball game without reg_keys playing? __R Sent from my BlackBerry 10 smartphone. From: Waite, Dick (External) Sent: Saturday, 25 November 2017 07:01 To: 'sle-beta at lists.suse.com' Cc: 'Vincent Moutoussamy' Subject: RE: Upgrade Beta3 All seems well bar the "SUSE Linux Enterprise Development Kit 12 SP3" which is in RED and says it will be removed, but it's marked as an error and it's stopping the ball rolling. Anyway time to go to the day job, sort out some issues with Windows 10 RS4 ;o) Have you all a very grand day. __R ________________________________ From: Waite, Dick (External) Sent: 25 November 2017 02:33 To: 'sle-beta at lists.suse.com' Cc: 'Vincent Moutoussamy' Subject: RE: Upgrade Beta3 I had a glass of Irish... SUSEConnect --cleanup to remove all registration trace. shutdown -r now upgrade as the words say, it's a big bumpy but along this track you do get into upgrade mode... Seems if the system knows it's registered it pop's off home... More in the morning, I'll let this update tonight. __R ________________________________ From: Waite, Dick (External) Sent: 25 November 2017 01:55 To: 'sle-beta at lists.suse.com' Cc: 'Vincent Moutoussamy' Subject: Upgrade Beta3 Grand Night, A new install ran Okay. I tried an offline migration using the installer and package: Finds the old version Okay then pops off to the SCC and you then get a "No migration product found". I tried with out a network and then I get an internal error. Need to stop it asking home about an update.... Migration from SLE 12 to SLE 15 With Beta 3, we are still not in an ideal state for the support of the different migration scenarios from SLE 12 to SLE 15. You can try it but it is not expected to be smooth! Nevertheless do not hesitate to share your findings if you face any issues, but keep in mind that we are working on it. * Offline migration: With Beta 3, it is possible by using the SLE-15-Installer and SLE-15-Packages isos. __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From malcolmlewis at cableone.net Sat Nov 25 09:44:49 2017 From: malcolmlewis at cableone.net (Malcolm) Date: Sat, 25 Nov 2017 10:44:49 -0600 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> Message-ID: <20171125104303.48e9c5da@grover.homelinux.org> On Fri, 24 Nov 2017 19:47:52 +0100 Vincent Moutoussamy wrote: > Hi, > > > On 24 Nov 2017, at 18:02, Malcolm > > wrote: > > > > On Fri, 24 Nov 2017 17:37:42 +0100 > > SUSE Beta Program > > wrote: > >> Here comes Beta 3 of SUSE Linux Enterprise 15: > >> SUSE Linux Enterprise Server (SLES), > >> SUSE Linux Enterprise Desktop (SLED), > >> SUSE Linux Enterprise High Availability (SLE-HA), > >> and SUSE Linux Enterprise Workstation Extension (SLE-WE) > >> > > Hi > > Can some kind person update the checksums.. specifically SHA256SUMS > > for Beta 3. > > What?s wrong with it? Maybe our browser cache or our CDN is playing > some tricks. > Hi Apologies for the direct reply in my previous email, I still see the Beta 2 SHA256SUMS here in the US? https://download.suse.com/protected/Summary.jsp?buildid=C9WijZq1Z4Q~ -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.92-18.36-default HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 up 11 days 14:05, 1 user, load average: 0.83, 1.27, 0.99 From Dick.Waite at softwareag.com Sun Nov 26 00:20:05 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Sun, 26 Nov 2017 07:20:05 +0000 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag>, <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> Grand Sunday, To be able to run an "Upgrade" or "Migration" one has to remove the registration key. From the many tries I have done over the past days if the environment has a SLES12 or SLES15 key valid then it "calls home" and home says "sorry don't know what your on about." If you disable network to stop the call home, then you get "an internal error". So SUSE wise people, is it correct that the key must be removed ? In my case with the key removed then you do move into the update/migration space.. My next stopper was the SDK, see attached png. As all my machine have the SDK so an issue. Another pnc show the selection of what modules one can use. I'm sure when the Docu is available each will be describe, I ticked a few to see what happened. I did get an update built, attached, but on the re-ipl it gave a flashing screen and warnings about VMware ;o) SUSE if you do have a little Docu, in Beta form, it would be interesting to read about YOUR thought on how UPdate/migration could be tried with Beta3 that would be grand. __R ________________________________ From: Waite, Dick (External) Sent: 25 November 2017 02:33 To: 'sle-beta at lists.suse.com' Cc: 'Vincent Moutoussamy' Subject: RE: Upgrade Beta3 I had a glass of Irish... SUSEConnect --cleanup to remove all registration trace. shutdown -r now upgrade as the words say, it's a big bumpy but along this track you do get into upgrade mode... Seems if the system knows it's registered it pop's off home... More in the morning, I'll let this update tonight. __R ________________________________ From: Waite, Dick (External) Sent: 25 November 2017 01:55 To: 'sle-beta at lists.suse.com' Cc: 'Vincent Moutoussamy' Subject: Upgrade Beta3 Grand Night, A new install ran Okay. I tried an offline migration using the installer and package: Finds the old version Okay then pops off to the SCC and you then get a "No migration product found". I tried with out a network and then I get an internal error. Need to stop it asking home about an update.... Migration from SLE 12 to SLE 15 With Beta 3, we are still not in an ideal state for the support of the different migration scenarios from SLE 12 to SLE 15. You can try it but it is not expected to be smooth! Nevertheless do not hesitate to share your findings if you face any issues, but keep in mind that we are working on it. * Offline migration: With Beta 3, it is possible by using the SLE-15-Installer and SLE-15-Packages isos. __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Clone-rjw9-12-3-01-2017-11-25-10-24-03.png Type: image/png Size: 111721 bytes Desc: Clone-rjw9-12-3-01-2017-11-25-10-24-03.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Clone-rjw9-12-3-01-2017-11-25-10-51-07.png Type: image/png Size: 50856 bytes Desc: Clone-rjw9-12-3-01-2017-11-25-10-51-07.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Clone-rjw9-12-3-01-2017-11-25-10-51-13.png Type: image/png Size: 47958 bytes Desc: Clone-rjw9-12-3-01-2017-11-25-10-51-13.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Clone-rjw9-12-3-01-2017-11-25-11-11-55.png Type: image/png Size: 88497 bytes Desc: Clone-rjw9-12-3-01-2017-11-25-11-11-55.png URL: From jrd at netlab1.net Sun Nov 26 09:04:39 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Sun, 26 Nov 2017 16:04:39 +0000 Subject: [sle-beta] Beta3 post install software installation In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> Message-ID: <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> ??? I have run into two problems just after installation of beta 3. ??? If I ask YaST to allow me to inspect and install further software then the process blocks with a popup which reduces to curl being unable to find the local issuer's SSL certificate, curl error 60. The repositories are those on SUSE, straight from the installation process. ??? Directory /etc/ssl/private is empty, thus no self signed certs. Adding my proper certs into /etc/ssl/servercerts, and symlinking /etc/ssl/private to that same directory has not improved things. Then looking more carefully at /etc/ssl I find a large vacuum where CA certs ought to be, empty space populated by only a lonely file named openssl.cnf. ??? Taking a space walk into that problem, I went into YaST | Software, asked about "certificate", got a list of installed candidates, chose ca-certificates, got a warning popup which says I must uninstall openssl v1.1 and install v1.0.2l. Hmmm, I had thought certificates were impervious to editions of openssl, being rather separate operations, but now we see them glued together. Not what I expected nor can use. ??? Not to be stopped by mere failures, I told YaST to use option 3, break dependencies for the ca-certificates item. It responded with an error popup which said it could not contact SUSE to do this chore. At this point I have that "Catch-22" feeling. It starts with certificates being absent, and matters slide downhill from there. ??? What might be acting in this case is I have selected to install OpenSSL v1.1 rather than the default v1.0.2. The SSL selection part also indicates awkwardness which needs attention. That is, YaST does not wish to allow me to install the SSL libraries for both versions of SSL, even though the libraries do cohabit on earlier SLES's. My normal drill is install two libraries, then when building things install the appropriate -devel version so that the desired SSL version headers are used. ??? Tis a puzzle at this moment. ??? Thanks, ??? Joe D. From jsrain at suse.cz Sun Nov 26 23:32:51 2017 From: jsrain at suse.cz (Jiri Srain) Date: Mon, 27 Nov 2017 07:32:51 +0100 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> Message-ID: <9be9a236-386f-2045-3e92-ce100eda3a5b@suse.cz> Hello, there are two ways to upgrade SLES12 to SLES15 planned: 1. Using the repos from SCC. In this case, system needs to be registered and the new repositories are delivered form SCC. This is not yet implemented with Beta3 2. Fully off-line (meaning no SCC, does not matter whether you use the modules media or their local HTTP mirror), where you need to select needed modules manually; however, this requires the system not to be registered, because otherwise it ends up with mix of SLES12 and SLES15 repositories. You can re-register the system after upgrade, though. HTH, Jiri On 25.11.2017 02:33, Waite, Dick (External) wrote: > I had a glass of Irish... > > SUSEConnect --cleanup? to remove all registration trace. > > shutdown -r now > > upgrade > > as the words say, it's a big bumpy but along this track you do get into > upgrade mode... Seems if the system knows it's registered it pop's off > home... > > More in the morning, I'll let this update tonight. > > __R > ------------------------------------------------------------------------ > *From:* Waite, Dick (External) > *Sent:* 25 November 2017 01:55 > *To:* 'sle-beta at lists.suse.com' > *Cc:* 'Vincent Moutoussamy' > *Subject:* Upgrade Beta3 > > Grand Night, > > A new install ran Okay. > > I tried an offline migration using the installer and package: > > Finds the old version Okay then pops off to the SCC and you then get a > "No migration product found". I tried with out a network and then I get > an internal error. > > Need to stop it asking home about an update.... > > > Migration from SLE 12 to SLE 15 > > With Beta 3, we are still not in an ideal state for the support of the > different migration scenarios from SLE 12 to SLE 15. You can try it but > it is not expected to be smooth! Nevertheless do not hesitate to share > your findings if you face any issues, but keep in mind that we are > working on it. > > * *Offline migration:* With Beta 3, it is possible by using the > *SLE-15-Installer* and *SLE-15-Packages* isos. > > > __R > > > Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, > Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - > Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), > Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - > Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas > Bereczky - *http://www.softwareag.com* > > > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Krizikova 148/34 tel: +420 284 084 659 186 00 Praha 8 fax: +420 284 084 001 Czech Republic http://www.suse.com From Dick.Waite at softwareag.com Sun Nov 26 23:52:16 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 27 Nov 2017 06:52:16 +0000 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <9be9a236-386f-2045-3e92-ce100eda3a5b@suse.cz> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag>, <9be9a236-386f-2045-3e92-ce100eda3a5b@suse.cz> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A35@daeexmbx1.eur.ad.sag> Many Thanks Jiri, I'm happy with the off-line, any idea why the SDK of SLES12-SP-3 seems to give issues ? __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Jiri Srain [jsrain at suse.cz] Sent: 27 November 2017 07:32 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] Upgrade Beta3 Hello, there are two ways to upgrade SLES12 to SLES15 planned: 1. Using the repos from SCC. In this case, system needs to be registered and the new repositories are delivered form SCC. This is not yet implemented with Beta3 2. Fully off-line (meaning no SCC, does not matter whether you use the modules media or their local HTTP mirror), where you need to select needed modules manually; however, this requires the system not to be registered, because otherwise it ends up with mix of SLES12 and SLES15 repositories. You can re-register the system after upgrade, though. HTH, Jiri On 25.11.2017 02:33, Waite, Dick (External) wrote: > I had a glass of Irish... > > SUSEConnect --cleanup to remove all registration trace. > > shutdown -r now > > upgrade > > as the words say, it's a big bumpy but along this track you do get into > upgrade mode... Seems if the system knows it's registered it pop's off > home... > > More in the morning, I'll let this update tonight. > > __R > ------------------------------------------------------------------------ > *From:* Waite, Dick (External) > *Sent:* 25 November 2017 01:55 > *To:* 'sle-beta at lists.suse.com' > *Cc:* 'Vincent Moutoussamy' > *Subject:* Upgrade Beta3 > > Grand Night, > > A new install ran Okay. > > I tried an offline migration using the installer and package: > > Finds the old version Okay then pops off to the SCC and you then get a > "No migration product found". I tried with out a network and then I get > an internal error. > > Need to stop it asking home about an update.... > > > Migration from SLE 12 to SLE 15 > > With Beta 3, we are still not in an ideal state for the support of the > different migration scenarios from SLE 12 to SLE 15. You can try it but > it is not expected to be smooth! Nevertheless do not hesitate to share > your findings if you face any issues, but keep in mind that we are > working on it. > > * *Offline migration:* With Beta 3, it is possible by using the > *SLE-15-Installer* and *SLE-15-Packages* isos. > > > __R > > > Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, > Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - > Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), > Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - > Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas > Bereczky - *http://www.softwareag.com* > > > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Krizikova 148/34 tel: +420 284 084 659 186 00 Praha 8 fax: +420 284 084 001 Czech Republic http://www.suse.com _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta From Dick.Waite at softwareag.com Sun Nov 26 23:54:49 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 27 Nov 2017 06:54:49 +0000 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A35@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag>, <9be9a236-386f-2045-3e92-ce100eda3a5b@suse.cz>, <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A35@daeexmbx1.eur.ad.sag> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A78@daeexmbx1.eur.ad.sag> ...and can the Workstation Ext. be updated/migrated in the off-line mode ? __R ________________________________________ From: Waite, Dick (External) Sent: 27 November 2017 07:52 To: Jiri Srain; sle-beta at lists.suse.com Subject: RE: [sle-beta] Upgrade Beta3 Many Thanks Jiri, I'm happy with the off-line, any idea why the SDK of SLES12-SP-3 seems to give issues ? __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Jiri Srain [jsrain at suse.cz] Sent: 27 November 2017 07:32 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] Upgrade Beta3 Hello, there are two ways to upgrade SLES12 to SLES15 planned: 1. Using the repos from SCC. In this case, system needs to be registered and the new repositories are delivered form SCC. This is not yet implemented with Beta3 2. Fully off-line (meaning no SCC, does not matter whether you use the modules media or their local HTTP mirror), where you need to select needed modules manually; however, this requires the system not to be registered, because otherwise it ends up with mix of SLES12 and SLES15 repositories. You can re-register the system after upgrade, though. HTH, Jiri On 25.11.2017 02:33, Waite, Dick (External) wrote: > I had a glass of Irish... > > SUSEConnect --cleanup to remove all registration trace. > > shutdown -r now > > upgrade > > as the words say, it's a big bumpy but along this track you do get into > upgrade mode... Seems if the system knows it's registered it pop's off > home... > > More in the morning, I'll let this update tonight. > > __R > ------------------------------------------------------------------------ > *From:* Waite, Dick (External) > *Sent:* 25 November 2017 01:55 > *To:* 'sle-beta at lists.suse.com' > *Cc:* 'Vincent Moutoussamy' > *Subject:* Upgrade Beta3 > > Grand Night, > > A new install ran Okay. > > I tried an offline migration using the installer and package: > > Finds the old version Okay then pops off to the SCC and you then get a > "No migration product found". I tried with out a network and then I get > an internal error. > > Need to stop it asking home about an update.... > > > Migration from SLE 12 to SLE 15 > > With Beta 3, we are still not in an ideal state for the support of the > different migration scenarios from SLE 12 to SLE 15. You can try it but > it is not expected to be smooth! Nevertheless do not hesitate to share > your findings if you face any issues, but keep in mind that we are > working on it. > > * *Offline migration:* With Beta 3, it is possible by using the > *SLE-15-Installer* and *SLE-15-Packages* isos. > > > __R > > > Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, > Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - > Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), > Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - > Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas > Bereczky - *http://www.softwareag.com* > > > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Krizikova 148/34 tel: +420 284 084 659 186 00 Praha 8 fax: +420 284 084 001 Czech Republic http://www.suse.com _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta From jsrain at suse.cz Sun Nov 26 23:59:11 2017 From: jsrain at suse.cz (Jiri Srain) Date: Mon, 27 Nov 2017 07:59:11 +0100 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A78@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <9be9a236-386f-2045-3e92-ce100eda3a5b@suse.cz> <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A35@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A78@daeexmbx1.eur.ad.sag> Message-ID: <70ee99dc-ea6d-e264-1d53-20e3c3858b92@suse.cz> Hello Dick, SDK does not exist any more with SLE15; as it does not have any clear successor product, YaST issues this warning. This is something that we will need to look into, however, I would probably postpone that until we have the upgrade paths configired in SCC (and adjust YaST's check the same way). I don't see any reason why any extension could not be upgraded off-line. You may run into the same issue as with SDK and you must make sure to add all necessary modules (there is no dependency evaluation between the repositories for the off-line upgrade). Jiri On 27.11.2017 07:54, Waite, Dick (External) wrote: > ...and can the Workstation Ext. be updated/migrated in the off-line mode ? > > __R > ________________________________________ > From: Waite, Dick (External) > Sent: 27 November 2017 07:52 > To: Jiri Srain; sle-beta at lists.suse.com > Subject: RE: [sle-beta] Upgrade Beta3 > > Many Thanks Jiri, > I'm happy with the off-line, any idea why the SDK of SLES12-SP-3 seems to give issues ? > > __R > ________________________________________ > From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Jiri Srain [jsrain at suse.cz] > Sent: 27 November 2017 07:32 > To: sle-beta at lists.suse.com > Subject: Re: [sle-beta] Upgrade Beta3 > > Hello, > > there are two ways to upgrade SLES12 to SLES15 planned: > > 1. Using the repos from SCC. In this case, system needs to be registered > and the new repositories are delivered form SCC. This is not yet > implemented with Beta3 > > 2. Fully off-line (meaning no SCC, does not matter whether you use the > modules media or their local HTTP mirror), where you need to select > needed modules manually; however, this requires the system not to be > registered, because otherwise it ends up with mix of SLES12 and SLES15 > repositories. You can re-register the system after upgrade, though. > > HTH, > Jiri > > On 25.11.2017 02:33, Waite, Dick (External) wrote: >> I had a glass of Irish... >> >> SUSEConnect --cleanup to remove all registration trace. >> >> shutdown -r now >> >> upgrade >> >> as the words say, it's a big bumpy but along this track you do get into >> upgrade mode... Seems if the system knows it's registered it pop's off >> home... >> >> More in the morning, I'll let this update tonight. >> >> __R >> ------------------------------------------------------------------------ >> *From:* Waite, Dick (External) >> *Sent:* 25 November 2017 01:55 >> *To:* 'sle-beta at lists.suse.com' >> *Cc:* 'Vincent Moutoussamy' >> *Subject:* Upgrade Beta3 >> >> Grand Night, >> >> A new install ran Okay. >> >> I tried an offline migration using the installer and package: >> >> Finds the old version Okay then pops off to the SCC and you then get a >> "No migration product found". I tried with out a network and then I get >> an internal error. >> >> Need to stop it asking home about an update.... >> >> >> Migration from SLE 12 to SLE 15 >> >> With Beta 3, we are still not in an ideal state for the support of the >> different migration scenarios from SLE 12 to SLE 15. You can try it but >> it is not expected to be smooth! Nevertheless do not hesitate to share >> your findings if you face any issues, but keep in mind that we are >> working on it. >> >> * *Offline migration:* With Beta 3, it is possible by using the >> *SLE-15-Installer* and *SLE-15-Packages* isos. >> >> >> __R >> >> >> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, >> Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - >> Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), >> Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - >> Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas >> Bereczky - *http://www.softwareag.com* >> >> >> >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta >> > > -- > Regards, > > Jiri Srain > Project Manager > --------------------------------------------------------------------- > SUSE LINUX, s.r.o. e-mail: jsrain at suse.com > Krizikova 148/34 tel: +420 284 084 659 > 186 00 Praha 8 fax: +420 284 084 001 > Czech Republic http://www.suse.com > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Krizikova 148/34 tel: +420 284 084 659 186 00 Praha 8 fax: +420 284 084 001 Czech Republic http://www.suse.com From Dick.Waite at softwareag.com Mon Nov 27 00:04:58 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 27 Nov 2017 07:04:58 +0000 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <70ee99dc-ea6d-e264-1d53-20e3c3858b92@suse.cz> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <9be9a236-386f-2045-3e92-ce100eda3a5b@suse.cz> <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A35@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A78@daeexmbx1.eur.ad.sag>, <70ee99dc-ea6d-e264-1d53-20e3c3858b92@suse.cz> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F6F2AD8@daeexmbx1.eur.ad.sag> Grand words Jiri, Understand the SDK and WSE. After my runs over the weekend I think I'll put the update/migration on hold and wait for Beta4. I think it does need a few more words in the Docu and I expect these will come with Beta4. December 7th is not so far away. Many Thanks, __R ________________________________________ From: Jiri Srain [jsrain at suse.cz] Sent: 27 November 2017 07:59 To: Waite, Dick (External); sle-beta at lists.suse.com Subject: Re: [sle-beta] Upgrade Beta3 Hello Dick, SDK does not exist any more with SLE15; as it does not have any clear successor product, YaST issues this warning. This is something that we will need to look into, however, I would probably postpone that until we have the upgrade paths configired in SCC (and adjust YaST's check the same way). I don't see any reason why any extension could not be upgraded off-line. You may run into the same issue as with SDK and you must make sure to add all necessary modules (there is no dependency evaluation between the repositories for the off-line upgrade). Jiri On 27.11.2017 07:54, Waite, Dick (External) wrote: > ...and can the Workstation Ext. be updated/migrated in the off-line mode ? > > __R > ________________________________________ > From: Waite, Dick (External) > Sent: 27 November 2017 07:52 > To: Jiri Srain; sle-beta at lists.suse.com > Subject: RE: [sle-beta] Upgrade Beta3 > > Many Thanks Jiri, > I'm happy with the off-line, any idea why the SDK of SLES12-SP-3 seems to give issues ? > > __R > ________________________________________ > From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Jiri Srain [jsrain at suse.cz] > Sent: 27 November 2017 07:32 > To: sle-beta at lists.suse.com > Subject: Re: [sle-beta] Upgrade Beta3 > > Hello, > > there are two ways to upgrade SLES12 to SLES15 planned: > > 1. Using the repos from SCC. In this case, system needs to be registered > and the new repositories are delivered form SCC. This is not yet > implemented with Beta3 > > 2. Fully off-line (meaning no SCC, does not matter whether you use the > modules media or their local HTTP mirror), where you need to select > needed modules manually; however, this requires the system not to be > registered, because otherwise it ends up with mix of SLES12 and SLES15 > repositories. You can re-register the system after upgrade, though. > > HTH, > Jiri > > On 25.11.2017 02:33, Waite, Dick (External) wrote: >> I had a glass of Irish... >> >> SUSEConnect --cleanup to remove all registration trace. >> >> shutdown -r now >> >> upgrade >> >> as the words say, it's a big bumpy but along this track you do get into >> upgrade mode... Seems if the system knows it's registered it pop's off >> home... >> >> More in the morning, I'll let this update tonight. >> >> __R >> ------------------------------------------------------------------------ >> *From:* Waite, Dick (External) >> *Sent:* 25 November 2017 01:55 >> *To:* 'sle-beta at lists.suse.com' >> *Cc:* 'Vincent Moutoussamy' >> *Subject:* Upgrade Beta3 >> >> Grand Night, >> >> A new install ran Okay. >> >> I tried an offline migration using the installer and package: >> >> Finds the old version Okay then pops off to the SCC and you then get a >> "No migration product found". I tried with out a network and then I get >> an internal error. >> >> Need to stop it asking home about an update.... >> >> >> Migration from SLE 12 to SLE 15 >> >> With Beta 3, we are still not in an ideal state for the support of the >> different migration scenarios from SLE 12 to SLE 15. You can try it but >> it is not expected to be smooth! Nevertheless do not hesitate to share >> your findings if you face any issues, but keep in mind that we are >> working on it. >> >> * *Offline migration:* With Beta 3, it is possible by using the >> *SLE-15-Installer* and *SLE-15-Packages* isos. >> >> >> __R >> >> >> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, >> Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - >> Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), >> Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - >> Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas >> Bereczky - *http://www.softwareag.com* >> >> >> >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta >> > > -- > Regards, > > Jiri Srain > Project Manager > --------------------------------------------------------------------- > SUSE LINUX, s.r.o. e-mail: jsrain at suse.com > Krizikova 148/34 tel: +420 284 084 659 > 186 00 Praha 8 fax: +420 284 084 001 > Czech Republic http://www.suse.com > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Krizikova 148/34 tel: +420 284 084 659 186 00 Praha 8 fax: +420 284 084 001 Czech Republic http://www.suse.com From fcrozat at suse.com Mon Nov 27 02:11:54 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Mon, 27 Nov 2017 10:11:54 +0100 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <70ee99dc-ea6d-e264-1d53-20e3c3858b92@suse.cz> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <9be9a236-386f-2045-3e92-ce100eda3a5b@suse.cz> <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A35@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A78@daeexmbx1.eur.ad.sag> <70ee99dc-ea6d-e264-1d53-20e3c3858b92@suse.cz> Message-ID: <1511773914.31551.47.camel@suse.com> Le lundi 27 novembre 2017 ? 07:59 +0100, Jiri Srain a ?crit?: > Hello Dick, > > SDK does not exist any more with SLE15; as it does not have any clear > successor product, YaST issues this warning. This is something that > we > will need to look into, however, I would probably postpone that until > we > have the upgrade paths configired in SCC (and adjust YaST's check the > same way). > > I don't see any reason why any extension could not be upgraded off- > line. > You may run into the same issue as with SDK and you must make sure to > add all necessary modules (there is no dependency evaluation between > the > repositories for the off-line upgrade). Workstation extension is on the packages DVD under the name "Desktop Productivity". -- Frederic Crozat Enterprise Desktop Release Manager SUSE From Dick.Waite at softwareag.com Mon Nov 27 02:13:24 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 27 Nov 2017 09:13:24 +0000 Subject: [sle-beta] Upgrade Beta3 In-Reply-To: <1511773914.31551.47.camel@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <9be9a236-386f-2045-3e92-ce100eda3a5b@suse.cz> <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A35@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F2A78@daeexmbx1.eur.ad.sag> <70ee99dc-ea6d-e264-1d53-20e3c3858b92@suse.cz>, <1511773914.31551.47.camel@suse.com> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F6F2C54@daeexmbx1.eur.ad.sag> Many Thanks Frederic. __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Frederic Crozat [fcrozat at suse.com] Sent: 27 November 2017 10:11 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] Upgrade Beta3 Le lundi 27 novembre 2017 ? 07:59 +0100, Jiri Srain a ?crit : > Hello Dick, > > SDK does not exist any more with SLE15; as it does not have any clear > successor product, YaST issues this warning. This is something that > we > will need to look into, however, I would probably postpone that until > we > have the upgrade paths configired in SCC (and adjust YaST's check the > same way). > > I don't see any reason why any extension could not be upgraded off- > line. > You may run into the same issue as with SDK and you must make sure to > add all necessary modules (there is no dependency evaluation between > the > repositories for the off-line upgrade). Workstation extension is on the packages DVD under the name "Desktop Productivity". -- Frederic Crozat Enterprise Desktop Release Manager SUSE _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From vmoutoussamy at suse.com Mon Nov 27 02:53:32 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Mon, 27 Nov 2017 10:53:32 +0100 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <20171125104303.48e9c5da@grover.homelinux.org> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> Message-ID: <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> Hi, Please confirm that you see the SUMS files for Beta3. Whenever you face something similar, please try to use the private mode of your browser and force a refresh of the page. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 25 Nov 2017, at 17:44, Malcolm wrote: > > On Fri, 24 Nov 2017 19:47:52 +0100 > Vincent Moutoussamy wrote: > >> Hi, >> >>> On 24 Nov 2017, at 18:02, Malcolm >> > wrote: >>> >>> On Fri, 24 Nov 2017 17:37:42 +0100 >>> SUSE Beta Program >> > wrote: >>>> Here comes Beta 3 of SUSE Linux Enterprise 15: >>>> SUSE Linux Enterprise Server (SLES), >>>> SUSE Linux Enterprise Desktop (SLED), >>>> SUSE Linux Enterprise High Availability (SLE-HA), >>>> and SUSE Linux Enterprise Workstation Extension (SLE-WE) >>>> >>> Hi >>> Can some kind person update the checksums.. specifically SHA256SUMS >>> for Beta 3. >> >> What?s wrong with it? Maybe our browser cache or our CDN is playing >> some tricks. >> > Hi > Apologies for the direct reply in my previous email, I still see the > Beta 2 SHA256SUMS here in the US? > > https://download.suse.com/protected/Summary.jsp?buildid=C9WijZq1Z4Q~ > > -- > Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) > openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.92-18.36-default > HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 > up 11 days 14:05, 1 user, load average: 0.83, 1.27, 0.99 > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From ext-linus.larsson at se.fujitsu.com Mon Nov 27 05:32:10 2017 From: ext-linus.larsson at se.fujitsu.com (ext-linus.larsson at se.fujitsu.com) Date: Mon, 27 Nov 2017 12:32:10 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <5a184ad6a143f_1a025dd3247222a@boucane.mail> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> Message-ID: <1511785930185.57447@se.fujitsu.com> Hi, When will support for building our own packages be fully added? Still missing at least these;? post-build-checks rpmlint-Factory build-compare brp-extract-appdata Without them we can't build on OBS. From: sle-beta-bounces at lists.suse.com on behalf of SUSE Beta Program Sent: Friday, November 24, 2017 17:37 To: sle-beta at lists.suse.com Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! ? Having trouble viewing this email? Please check the plain text version of it with your mailer. ? ? ? Here comes Beta 3 of SUSE Linux Enterprise 15 for: SUSE Linux Enterprise Server (SLES), SUSE Linux Enterprise Desktop (SLED), SUSE Linux Enterprise Workstation Extension (SLE-WE), SUSE Linux Enterprise High Availablility (SLE-HA) Download ? Important Notice Online Channels for Beta 3At the time of this announcement, our SCC online channels synchronisations are still in progress. We expect them to finish in a few hours, in the mean time you need to use the SLE-15-Installer and SLE-15-Packages isos for your testing. Migration from SLE 12 to SLE 15With Beta 3, we are still not in an ideal state for the support of the different migration scenarios from SLE 12 to SLE 15. You can try it but it is not expected to be smooth! Nevertheless do not hesitate to share your findings if you face any issues, but keep in mind that we are working on it. Offline migration: With Beta 3, it is possible by using the SLE-15-Installer and SLE-15-Packages isos. Online migration: Not possible with Beta 3, the SCC setup of the online channels still needs adaptation. We hope to get this done for future beta releases. More information SLE Beta Page ? Release Notes ? Known Issues ? ? Your SUSE Linux Enterprise Team ? Do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Click here to unsubscribe. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? From vmoutoussamy at suse.com Mon Nov 27 08:14:34 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Mon, 27 Nov 2017 16:14:34 +0100 Subject: [sle-beta] Beta3 post install software installation In-Reply-To: <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> Message-ID: <2BBAE913-3BB9-4C63-9B1A-65C18FB8F2E4@suse.com> Hi, Can you easily reproduce this issue? The ?curl error 60? was the starting point issue right? Could you please retrieve a supportconfig and yastlogs* and open a bug report? A fresh install with the error would be great! Regards, * https://www.suse.com/betaprogram/beta-guidelines/#q14 -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 26 Nov 2017, at 17:04, Joe Doupnik wrote: > > I have run into two problems just after installation of beta 3. > If I ask YaST to allow me to inspect and install further software then the process blocks with a popup which reduces to curl being unable to find the local issuer's SSL certificate, curl error 60. The repositories are those on SUSE, straight from the installation process. > Directory /etc/ssl/private is empty, thus no self signed certs. Adding my proper certs into /etc/ssl/servercerts, and symlinking /etc/ssl/private to that same directory has not improved things. Then looking more carefully at /etc/ssl I find a large vacuum where CA certs ought to be, empty space populated by only a lonely file named openssl.cnf. > Taking a space walk into that problem, I went into YaST | Software, asked about "certificate", got a list of installed candidates, chose ca-certificates, got a warning popup which says I must uninstall openssl v1.1 and install v1.0.2l. Hmmm, I had thought certificates were impervious to editions of openssl, being rather separate operations, but now we see them glued together. Not what I expected nor can use. > Not to be stopped by mere failures, I told YaST to use option 3, break dependencies for the ca-certificates item. It responded with an error popup which said it could not contact SUSE to do this chore. At this point I have that "Catch-22" feeling. It starts with certificates being absent, and matters slide downhill from there. > What might be acting in this case is I have selected to install OpenSSL v1.1 rather than the default v1.0.2. The SSL selection part also indicates awkwardness which needs attention. That is, YaST does not wish to allow me to install the SSL libraries for both versions of SSL, even though the libraries do cohabit on earlier SLES's. My normal drill is install two libraries, then when building things install the appropriate -devel version so that the desired SSL version headers are used. > Tis a puzzle at this moment. > Thanks, > Joe D. > > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From jrd at netlab1.net Mon Nov 27 08:19:32 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Mon, 27 Nov 2017 15:19:32 +0000 Subject: [sle-beta] Beta3 post install software installation In-Reply-To: <2BBAE913-3BB9-4C63-9B1A-65C18FB8F2E4@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> <2BBAE913-3BB9-4C63-9B1A-65C18FB8F2E4@suse.com> Message-ID: Vincent, ??? Yes, I will try to prepare a findings bundle to help diagnose matters. Give me a day to do this (fresh install with no Openssl v1.1 choice, test things, then a fresh install with the v1.1 choice plus adding to the evidence bundle). ??? Thanks, ??? Joe D. On 27/11/2017 15:14, Vincent Moutoussamy wrote: > Hi, > > Can you easily reproduce this issue? > > The ?curl error 60? was the starting point issue right? > Could you please retrieve a supportconfig and yastlogs* and open a bug report? > A fresh install with the error would be great! > > Regards, > > * https://www.suse.com/betaprogram/beta-guidelines/#q14 > -- > Vincent Moutoussamy > SUSE Beta Program and SDK Project Manager > > > >> On 26 Nov 2017, at 17:04, Joe Doupnik wrote: >> >> I have run into two problems just after installation of beta 3. >> If I ask YaST to allow me to inspect and install further software then the process blocks with a popup which reduces to curl being unable to find the local issuer's SSL certificate, curl error 60. The repositories are those on SUSE, straight from the installation process. >> Directory /etc/ssl/private is empty, thus no self signed certs. Adding my proper certs into /etc/ssl/servercerts, and symlinking /etc/ssl/private to that same directory has not improved things. Then looking more carefully at /etc/ssl I find a large vacuum where CA certs ought to be, empty space populated by only a lonely file named openssl.cnf. >> Taking a space walk into that problem, I went into YaST | Software, asked about "certificate", got a list of installed candidates, chose ca-certificates, got a warning popup which says I must uninstall openssl v1.1 and install v1.0.2l. Hmmm, I had thought certificates were impervious to editions of openssl, being rather separate operations, but now we see them glued together. Not what I expected nor can use. >> Not to be stopped by mere failures, I told YaST to use option 3, break dependencies for the ca-certificates item. It responded with an error popup which said it could not contact SUSE to do this chore. At this point I have that "Catch-22" feeling. It starts with certificates being absent, and matters slide downhill from there. >> What might be acting in this case is I have selected to install OpenSSL v1.1 rather than the default v1.0.2. The SSL selection part also indicates awkwardness which needs attention. That is, YaST does not wish to allow me to install the SSL libraries for both versions of SSL, even though the libraries do cohabit on earlier SLES's. My normal drill is install two libraries, then when building things install the appropriate -devel version so that the desired SSL version headers are used. >> Tis a puzzle at this moment. >> Thanks, >> Joe D. >> >> >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta From malcolmlewis at cableone.net Mon Nov 27 10:08:53 2017 From: malcolmlewis at cableone.net (Malcolm) Date: Mon, 27 Nov 2017 11:08:53 -0600 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> Message-ID: <20171127110853.6fe8077c@grover.homelinux.org> On Mon, 27 Nov 2017 10:53:32 +0100 Vincent Moutoussamy wrote: > Hi, > > Please confirm that you see the SUMS files for Beta3. Whenever you > face something similar, please try to use the private mode of your > browser and force a refresh of the page. > > Regards, Hi All very strange.... I've tried multiple systems with Firefox, including a private browsing window, refreshing etc. Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED 15 Beta3, SLES 12 SP3 and Windows 10. I've tried cleared cookies and history yet still only see the md5, sha1 and sha256 sums for beta 2..... -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.92-18.36-default HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 up 13 days 14:26, 1 user, load average: 0.05, 0.69, 0.90 From S.M.Flood at uis.cam.ac.uk Mon Nov 27 10:16:50 2017 From: S.M.Flood at uis.cam.ac.uk (Simon Flood) Date: Mon, 27 Nov 2017 17:16:50 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <20171127110853.6fe8077c@grover.homelinux.org> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> Message-ID: <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> On 27/11/17 17:08, Malcolm wrote: > All very strange.... I've tried multiple systems with Firefox, including > a private browsing window, refreshing etc. > > Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED > 15 Beta3, SLES 12 SP3 and Windows 10. > > I've tried cleared cookies and history yet still only see the md5, sha1 > and sha256 sums for beta 2..... Ditto, I'm also seeing Beta 2 *SUMS. Just tried Firefox private window on openSUSE Leap 42.2. HTH, Simon -- Simon Flood HPC System Administrator University of Cambridge Information Services United Kingdom SUSE Knowledge Partner From Dick.Waite at softwareag.com Mon Nov 27 10:27:00 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Mon, 27 Nov 2017 17:27:00 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org>, <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> Grand Evening, This is what I see on an oldish Firefox that did down load the installer and packages for Beta3 on x86_64 and s390x.... So I think something is not quite right...with the SUMS, all three say Beat2... e3bbc395ff30f16bbba9e419244d8cd0 SLE-15-Installer-DVD-aarch64-Beta2-DVD1.iso 0dce5155cf6031f4ffb57a2b59430088 SLE-15-Installer-DVD-aarch64-Beta2-DVD2.iso 09fcadd42edebc9cd8c3fad3e8e454b5 SLE-15-Installer-DVD-aarch64-Beta2-DVD3.iso e4407bf89c20e6f9730c5102bea59e49 SLE-15-Installer-DVD-ppc64le-Beta2-DVD1.iso 9840dc57392d16954e1fe529ff3dca79 SLE-15-Installer-DVD-ppc64le-Beta2-DVD2.iso bb6879f45eb1174ceca4bf2cc701c3cf SLE-15-Installer-DVD-ppc64le-Beta2-DVD3.iso 37138e90b2584c8a8651fcde424adf38 SLE-15-Installer-DVD-s390x-Beta2-DVD1.iso 99e3a92e22005d66c3efb08536bc4f57 SLE-15-Installer-DVD-s390x-Beta2-DVD2.iso 04374427a532d57f37858e8c578f7b05 SLE-15-Installer-DVD-s390x-Beta2-DVD3.iso 48c6a6d9622ae31d86d5e3482aa5ba7a SLE-15-Installer-DVD-x86_64-Beta2-DVD1.iso e7cdcba0d8d1917780c74e2e3860ac9e SLE-15-Installer-DVD-x86_64-Beta2-DVD2.iso 45c1dd3ffc15f02f48570d0b0dfcb2a4 SLE-15-Installer-DVD-x86_64-Beta2-DVD3.iso 0bf87ff258cd06d7ffacbb368813f8a4 SLE-15-Packages-aarch64-Beta2-DVD1.iso a6156fdcf01629fe03e72b3482c4749f SLE-15-Packages-aarch64-Beta2-DVD2.iso f31dac8c8e2b0075553a0875e5ca2aa6 SLE-15-Packages-aarch64-Beta2-DVD3.iso 1e43617eaa23b54b22f329b486e3c066 SLE-15-Packages-ppc64le-Beta2-DVD1.iso 3a0d49079a3169ad2740393e6bebde51 SLE-15-Packages-ppc64le-Beta2-DVD2.iso cba96ef34ff4aecf169293fb26482d81 SLE-15-Packages-ppc64le-Beta2-DVD3.iso d2919db1e83057b8047a0f4b85396e01 SLE-15-Packages-s390x-Beta2-DVD1.iso b969f2de5d08550800b4b3dd54787d5e SLE-15-Packages-s390x-Beta2-DVD2.iso ff12e87f375419d46edb28d1c6782434 SLE-15-Packages-s390x-Beta2-DVD3.iso c9334dc3369982245e8d550d88ed4387 SLE-15-Packages-x86_64-Beta2-DVD1.iso 2bea089918cd7cf1e85a4e1aaaf784c3 SLE-15-Packages-x86_64-Beta2-DVD2.iso 2458649b116b2561db9247f3ff213d03 SLE-15-Packages-x86_64-Beta2-DVD3.iso __R ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Simon Flood [S.M.Flood at uis.cam.ac.uk] Sent: 27 November 2017 18:16 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! On 27/11/17 17:08, Malcolm wrote: > All very strange.... I've tried multiple systems with Firefox, including > a private browsing window, refreshing etc. > > Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED > 15 Beta3, SLES 12 SP3 and Windows 10. > > I've tried cleared cookies and history yet still only see the md5, sha1 > and sha256 sums for beta 2..... Ditto, I'm also seeing Beta 2 *SUMS. Just tried Firefox private window on openSUSE Leap 42.2. HTH, Simon -- Simon Flood HPC System Administrator University of Cambridge Information Services United Kingdom SUSE Knowledge Partner _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From donald.buchholz at intel.com Mon Nov 27 10:46:54 2017 From: donald.buchholz at intel.com (Don Buchholz) Date: Mon, 27 Nov 2017 09:46:54 -0800 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> Message-ID: <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> On 11/27/2017 09:27 AM, Waite, Dick (External) wrote: > Grand Evening, > > This is what I see on an oldish Firefox that did down load the installer and packages for Beta3 on x86_64 and s390x.... So I think something is not quite right...with the SUMS, all three say Beat2... > > e3bbc395ff30f16bbba9e419244d8cd0 SLE-15-Installer-DVD-aarch64-Beta2-DVD1.iso > 0dce5155cf6031f4ffb57a2b59430088 SLE-15-Installer-DVD-aarch64-Beta2-DVD2.iso > 09fcadd42edebc9cd8c3fad3e8e454b5 SLE-15-Installer-DVD-aarch64-Beta2-DVD3.iso > ... -- -- ... > ________________________________________ > From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Simon Flood [S.M.Flood at uis.cam.ac.uk] > Sent: 27 November 2017 18:16 > To: sle-beta at lists.suse.com > Subject: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! > > On 27/11/17 17:08, Malcolm wrote: > >> All very strange.... I've tried multiple systems with Firefox, including >> a private browsing window, refreshing etc. >> >> Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED >> 15 Beta3, SLES 12 SP3 and Windows 10. >> >> I've tried cleared cookies and history yet still only see the md5, sha1 >> and sha256 sums for beta 2..... > Ditto, I'm also seeing Beta 2 *SUMS. Just tried Firefox private window > on openSUSE Leap 42.2. > Ditto. I just tried from a couple of different systems and three browsers here. (I'm 100% sure the Windows system using Internet Explorer has never hit the Beta download page before.) All system/browser combinations still have "SLE-15-*-Beta2-*.iso" checksums. - Don From Dick.Waite at softwareag.com Mon Nov 27 23:28:22 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Tue, 28 Nov 2017 06:28:22 +0000 Subject: [sle-beta] What version of SLES12 will Update / Migrate Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F70C4E1@daeexmbx1.eur.ad.sag> Just a question? What version / patch level should a SLES12 machine be running for a Update / Migration to run. That is when Update / Migration is available. I was thinking of making sure my machines were at the ?right? level. Can it be any SP version of SLES12 ? __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbrown at suse.de Tue Nov 28 01:20:19 2017 From: rbrown at suse.de (Richard Brown) Date: Tue, 28 Nov 2017 09:20:19 +0100 Subject: [sle-beta] What version of SLES12 will Update / Migrate In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F70C4E1@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F70C4E1@daeexmbx1.eur.ad.sag> Message-ID: <1511857219.16370.8.camel@suse.de> On Tue, 2017-11-28 at 06:28 +0000, Waite, Dick (External) wrote: > Just a question? > > What version / patch level should a SLES12 machine be running for a Update / Migration to run. That is when Update / Migration is available. I was thinking of making sure my machines were at the ?right? level. Can it be any SP version of SLES12 ? > > __R I believe we're working towards the supported options being both SLE 12 SP3 & SP4 -- Richard Brown Linux Distribution Engineer - Future Technology Team Chairman - openSUSE Phone +4991174053-361 SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From jsrain at suse.cz Tue Nov 28 01:55:51 2017 From: jsrain at suse.cz (Jiri Srain) Date: Tue, 28 Nov 2017 09:55:51 +0100 Subject: [sle-beta] Upgrade Beta3 - SDK Issues In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F7080F6@daeexmbx1.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D011F7080F6@daeexmbx1.eur.ad.sag> Message-ID: Hello Dick, the workaround for this scenario is: Enter the package selector, find the product (resp. its corresponding -release package) and mark it for deletion. Normally the package (and product) are selected for deleting by the dependency solver, which may result in accidental deleting of a product and this is why YaST warns you. When you select it explicitly for removal, YaST will treat it as your decision and accept it. Jiri On 27.11.2017 17:13, Waite, Dick (External) wrote: > Hi Jiri, > > Had a little time so I tried a simple QE machine. It was updated to SLES12-SP3 + today's UP and the reg_key removed. > > I get the issue with the SDK and from what I can see it is marked for delete. I have added a few screen shots in that area.... What should I do to be able to move forward ? > > __R > > ________________________________________ > From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Jiri Srain [jsrain at suse.cz] > Sent: 27 November 2017 07:32 > To: sle-beta at lists.suse.com > Subject: Re: [sle-beta] Upgrade Beta3 > > Hello, > > there are two ways to upgrade SLES12 to SLES15 planned: > > 1. Using the repos from SCC. In this case, system needs to be registered > and the new repositories are delivered form SCC. This is not yet > implemented with Beta3 > > 2. Fully off-line (meaning no SCC, does not matter whether you use the > modules media or their local HTTP mirror), where you need to select > needed modules manually; however, this requires the system not to be > registered, because otherwise it ends up with mix of SLES12 and SLES15 > repositories. You can re-register the system after upgrade, though. > > HTH, > Jiri > > On 25.11.2017 02:33, Waite, Dick (External) wrote: >> I had a glass of Irish... >> >> SUSEConnect --cleanup to remove all registration trace. >> >> shutdown -r now >> >> upgrade >> >> as the words say, it's a big bumpy but along this track you do get into >> upgrade mode... Seems if the system knows it's registered it pop's off >> home... >> >> More in the morning, I'll let this update tonight. >> >> __R >> ------------------------------------------------------------------------ >> *From:* Waite, Dick (External) >> *Sent:* 25 November 2017 01:55 >> *To:* 'sle-beta at lists.suse.com' >> *Cc:* 'Vincent Moutoussamy' >> *Subject:* Upgrade Beta3 >> >> Grand Night, >> >> A new install ran Okay. >> >> I tried an offline migration using the installer and package: >> >> Finds the old version Okay then pops off to the SCC and you then get a >> "No migration product found". I tried with out a network and then I get >> an internal error. >> >> Need to stop it asking home about an update.... >> >> >> Migration from SLE 12 to SLE 15 >> >> With Beta 3, we are still not in an ideal state for the support of the >> different migration scenarios from SLE 12 to SLE 15. You can try it but >> it is not expected to be smooth! Nevertheless do not hesitate to share >> your findings if you face any issues, but keep in mind that we are >> working on it. >> >> * *Offline migration:* With Beta 3, it is possible by using the >> *SLE-15-Installer* and *SLE-15-Packages* isos. >> >> >> __R >> >> >> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, >> Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - >> Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), >> Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - >> Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas >> Bereczky - *http://www.softwareag.com* >> >> >> >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta >> > > -- > Regards, > > Jiri Srain > Project Manager > --------------------------------------------------------------------- > SUSE LINUX, s.r.o. e-mail: jsrain at suse.com > Krizikova 148/34 tel: +420 284 084 659 > 186 00 Praha 8 fax: +420 284 084 001 > Czech Republic http://www.suse.com > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Krizikova 148/34 tel: +420 284 084 659 186 00 Praha 8 fax: +420 284 084 001 Czech Republic http://www.suse.com From fcrozat at suse.com Tue Nov 28 02:10:04 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 28 Nov 2017 10:10:04 +0100 Subject: [sle-beta] What version of SLES12 will Update / Migrate In-Reply-To: <1511857219.16370.8.camel@suse.de> References: <46AC8C81C10B8C48820201DF2AE1D76D011F70C4E1@daeexmbx1.eur.ad.sag> <1511857219.16370.8.camel@suse.de> Message-ID: <1511860204.16667.7.camel@suse.com> Le mardi 28 novembre 2017 ? 09:20 +0100, Richard Brown a ?crit?: > On Tue, 2017-11-28 at 06:28 +0000, Waite, Dick (External) wrote: > > > > Just a question? > > ? > > What version / patch level should a SLES12 machine be running for a > > Update / Migration to run. That is when Update / Migration is > > available. I was thinking of making sure my machines were at the > > ?right? level. Can it be any SP version of SLES12 ? > > ? > > __R > > I believe we're working towards the supported options being both SLE > 12 SP3 & SP4 We will only support migrating from SLE12 "supported" service pack, which means currently, 12 SP3 (and during lifetime of SLE15 GA, we will also support migrating from 12 SP4). -- Frederic Crozat Enterprise Desktop Release Manager SUSE From vmoutoussamy at suse.com Tue Nov 28 03:35:09 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 28 Nov 2017 11:35:09 +0100 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> Message-ID: <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> Hi, Ok so we definitely have a CDN issue for the SUMS files. I will escalate this issue but in the mean time could you please: - Tell us what?s current your location (city is enough)? - Report the output of ?dig cdn.microfocus.com ? Thank you all and sorry for the inconvenience, Regards, PS: SUMS files for Beta3 are attached. ? Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 27 Nov 2017, at 18:46, Don Buchholz > wrote: > > On 11/27/2017 09:27 AM, Waite, Dick (External) wrote: >> Grand Evening, >> >> This is what I see on an oldish Firefox that did down load the installer and packages for Beta3 on x86_64 and s390x.... So I think something is not quite right...with the SUMS, all three say Beat2... >> >> e3bbc395ff30f16bbba9e419244d8cd0 SLE-15-Installer-DVD-aarch64-Beta2-DVD1.iso >> 0dce5155cf6031f4ffb57a2b59430088 SLE-15-Installer-DVD-aarch64-Beta2-DVD2.iso >> 09fcadd42edebc9cd8c3fad3e8e454b5 SLE-15-Installer-DVD-aarch64-Beta2-DVD3.iso >> ... -- -- ... >> ________________________________________ >> From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com ] on behalf of Simon Flood [S.M.Flood at uis.cam.ac.uk ] >> Sent: 27 November 2017 18:16 >> To: sle-beta at lists.suse.com >> Subject: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! >> >> On 27/11/17 17:08, Malcolm wrote: >> >>> All very strange.... I've tried multiple systems with Firefox, including >>> a private browsing window, refreshing etc. >>> >>> Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED >>> 15 Beta3, SLES 12 SP3 and Windows 10. >>> >>> I've tried cleared cookies and history yet still only see the md5, sha1 >>> and sha256 sums for beta 2..... >> Ditto, I'm also seeing Beta 2 *SUMS. Just tried Firefox private window >> on openSUSE Leap 42.2. >> > > Ditto. I just tried from a couple of different systems and three browsers here. (I'm 100% sure the Windows system using Internet Explorer has never hit the Beta download page before.) All system/browser combinations still have "SLE-15-*-Beta2-*.iso" checksums. > > - Don > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: MD5SUMS Type: application/octet-stream Size: 1794 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SHA1SUMS Type: application/octet-stream Size: 1986 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SHA256SUMS Type: application/octet-stream Size: 2453 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From S.M.Flood at uis.cam.ac.uk Tue Nov 28 03:45:00 2017 From: S.M.Flood at uis.cam.ac.uk (Simon Flood) Date: Tue, 28 Nov 2017 10:45:00 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> Message-ID: <22b8c2d6-14b1-3847-5d16-f52b476c6e21@uis.cam.ac.uk> Here are the results from the UK (Cambridge) jury: ; <<>> DiG 9.9.9-P1 <<>> cdn.microfocus.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54866 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;cdn.microfocus.com. IN A ;; ANSWER SECTION: cdn.microfocus.com. 1800 IN CNAME cs640.cn.wpc.gammacdn.net. cs640.cn.wpc.gammacdn.net. 3600 IN CNAME cs640.wpc.apr-17a6a-2.edgecastdns.net. cs640.wpc.apr-17a6a-2.edgecastdns.net. 300 IN CNAME cs640.wpc.gammacdn.net. cs640.wpc.gammacdn.net. 3600 IN A 192.229.221.54 ;; Query time: 51 msec ;; SERVER: 131.111.12.20#53(131.111.12.20) ;; WHEN: Tue Nov 28 10:42:59 GMT 2017 ;; MSG SIZE rcvd: 170 HTH, Simon On 28/11/17 10:35, Vincent Moutoussamy wrote: > Hi, > > Ok so we definitely have a CDN issue for the SUMS files. > I will escalate this issue but in the mean time could you please: > - Tell us what?s current your location (city is enough)? > - Report the output of ?dig cdn.microfocus.com ? > > Thank you all and sorry for the inconvenience, > > Regards, > > PS: SUMS files for Beta3 are attached. > ? > Vincent Moutoussamy > SUSE Beta Program and SDK Project Manager > >> On 27 Nov 2017, at 18:46, Don Buchholz > > wrote: >> >> On 11/27/2017 09:27 AM, Waite, Dick (External) wrote: >>> Grand Evening, >>> >>> This is what I see on an oldish Firefox that did down load the installer and >>> packages for Beta3 on x86_64 and s390x.... So I think something is not quite >>> right...with the SUMS, all three say Beat2... >>> >>> e3bbc395ff30f16bbba9e419244d8cd0 SLE-15-Installer-DVD-aarch64-Beta2-DVD1.iso >>> 0dce5155cf6031f4ffb57a2b59430088 SLE-15-Installer-DVD-aarch64-Beta2-DVD2.iso >>> 09fcadd42edebc9cd8c3fad3e8e454b5 SLE-15-Installer-DVD-aarch64-Beta2-DVD3.iso >>> ... -- -- ... >>> ________________________________________ >>> From: sle-beta-bounces at lists.suse.com >>> [sle-beta-bounces at lists.suse.com >>> ] on behalf of Simon Flood >>> [S.M.Flood at uis.cam.ac.uk ] >>> Sent: 27 November 2017 18:16 >>> To: sle-beta at lists.suse.com >>> Subject: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! >>> >>> On 27/11/17 17:08, Malcolm wrote: >>> >>>> All very strange.... I've tried multiple systems with Firefox, including >>>> a private browsing window, refreshing etc. >>>> >>>> Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED >>>> 15 Beta3, SLES 12 SP3 and Windows 10. >>>> >>>> I've tried cleared cookies and history yet still only see the md5, sha1 >>>> and sha256 sums for beta 2..... >>> Ditto, I'm also seeing Beta 2 *SUMS. Just tried Firefox private window >>> on openSUSE Leap 42.2. >>> >> >> Ditto. I just tried from a couple of different systems and three browsers >> here. (I'm 100% sure the Windows system using Internet Explorer has never hit >> the Beta download page before.) All system/browser combinations still have >> "SLE-15-*-Beta2-*.iso" checksums. >> >> - Don >> >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta > -- Simon Flood HPC System Administrator University of Cambridge Information Services United Kingdom SUSE Knowledge Partner From malcolmlewis at cableone.net Tue Nov 28 05:04:23 2017 From: malcolmlewis at cableone.net (Malcolm) Date: Tue, 28 Nov 2017 06:04:23 -0600 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D011F70F7E1@daeexmbx1.eur.ad.sag> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D011F70F7E1@daeexmbx1.eur.ad.sag> Message-ID: <20171128060423.0e0c7b67@grover.homelinux.org> Hi Cleveland, Mississippi USA dig cdn.microfocus.com ; <<>> DiG 9.9.9-P1 <<>> cdn.microfocus.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33488 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;cdn.microfocus.com. IN A ;; ANSWER SECTION: cdn.microfocus.com. 1800 IN CNAME cs640.cn.wpc.gammacdn.net. cs640.cn.wpc.gammacdn.net. 3600 IN CNAME cs640.wpc.apr-17a6a-2.edgecastdns.net. cs640.wpc.apr-17a6a-2.edgecastdns.net. 300 IN CNAME cs640.wpc.gammacdn.net. cs640.wpc.gammacdn.net. 3600 IN A 192.229.211.66 ;; Query time: 54 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Tue Nov 28 06:01:49 CST 2017 ;; MSG SIZE rcvd: 170 -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.2 | GNOME 3.20.2 | 4.4.92-18.36-default HP 255 G4 Notebook | A6-6310 X4 @ 1.80 GHz | AMD Radeon R4 up 14 days 9:27, 1 user, load average: 1.64, 1.49, 0.91 From vmoutoussamy at suse.com Tue Nov 28 06:24:47 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 28 Nov 2017 14:24:47 +0100 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <1511785930185.57447@se.fujitsu.com> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <1511785930185.57447@se.fujitsu.com> Message-ID: <078513F0-176F-4D3B-9A1B-6A2A3AB99AD5@suse.com> Hi, > On 27 Nov 2017, at 13:32, ext-linus.larsson at se.fujitsu.com wrote: > > Hi, > > When will support for building our own packages be fully added? Still missing at least these;? > post-build-checks In the Packages iso: Development-Tools-OBS/noarch/post-build-checks-84.87+git20170929.5b244d1-1.1.noarch.rpm > rpmlint-Factory In the Packages iso: Development-Tools-OBS/noarch/rpmlint-Factory-1.0-3.1.noarch.rpm > build-compare In the Packages iso: Development-Tools-OBS/noarch/build-compare-20171108T070456.b855319-1.1.noarch.rpm > brp-extract-appdata I didn?t find this one in our medias, but there is already a bug for it: https://bugzilla.suse.com/show_bug.cgi?id=1067645 Please make yourself in CC of this bug to be kept in touch about any advancement. > > Without them we can't build on OBS. > Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > > > From: sle-beta-bounces at lists.suse.com on behalf of SUSE Beta Program > Sent: Friday, November 24, 2017 17:37 > To: sle-beta at lists.suse.com > Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! > > Having trouble viewing this email? Please check the plain text version of it with your mailer. > Here comes Beta 3 of SUSE Linux Enterprise 15 for: > SUSE Linux Enterprise Server (SLES), > SUSE Linux Enterprise Desktop (SLED), > SUSE Linux Enterprise Workstation Extension (SLE-WE), > SUSE Linux Enterprise High Availablility (SLE-HA) > > Download ? Important Notice Online Channels for Beta 3At the time of this announcement, our SCC online channels synchronisations are still in progress. We expect them to finish in a few hours, in the mean time you need to use the SLE-15-Installer and SLE-15-Packages isos for your testing. > Migration from SLE 12 to SLE 15With Beta 3, we are still not in an ideal state for the support of the different migration scenarios from SLE 12 to SLE 15. You can try it but it is not expected to be smooth! Nevertheless do not hesitate to share your findings if you face any issues, but keep in mind that we are working on it. > Offline migration: With Beta 3, it is possible by using the SLE-15-Installer and SLE-15-Packages isos. > Online migration: Not possible with Beta 3, the SCC setup of the online channels still needs adaptation. We hope to get this done for future beta releases. > More information SLE Beta Page ? Release Notes ? Known Issues ? Your SUSE Linux Enterprise Team > Do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. > You received this email because you're signed up to get updates from us. Click here to unsubscribe. > > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From Joerg.Reisenweber at btc-it-services.com Tue Nov 28 06:35:25 2017 From: Joerg.Reisenweber at btc-it-services.com (Joerg.Reisenweber at btc-it-services.com) Date: Tue, 28 Nov 2017 13:35:25 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> Message-ID: Oldenburg (Oldenburg), Germany: ; <<>> DiG 9.9.9-P1 <<>> cdn.microfocus.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13352 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;cdn.microfocus.com. IN A ;; ANSWER SECTION: cdn.microfocus.com. 1800 IN CNAME cs640.cn.wpc.gammacdn.net. cs640.cn.wpc.gammacdn.net. 3600 IN CNAME cs640.wpc.apr-17a6a-2.edgecastdns.net. cs640.wpc.apr-17a6a-2.edgecastdns.net. 300 IN CNAME cs640.wpc.gammacdn.net. cs640.wpc.gammacdn.net. 3600 IN A 192.229.221.54 ;; Query time: 98 msec ;; SERVER: 10.30.2.4#53(10.30.2.4) ;; WHEN: Tue Nov 28 14:34:28 CET 2017 ;; MSG SIZE rcvd: 170 Von: sle-beta-bounces at lists.suse.com [mailto:sle-beta-bounces at lists.suse.com] Im Auftrag von Vincent Moutoussamy Gesendet: Dienstag, 28. November 2017 11:35 An: sle-beta at lists.suse.com Betreff: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! Hi, Ok so we definitely have a CDN issue for the SUMS files. I will escalate this issue but in the mean time could you please: - Tell us what?s current your location (city is enough)? - Report the output of ?dig cdn.microfocus.com? Thank you all and sorry for the inconvenience, Regards, PS: SUMS files for Beta3 are attached. ? Vincent Moutoussamy SUSE Beta Program and SDK Project Manager On 27 Nov 2017, at 18:46, Don Buchholz > wrote: On 11/27/2017 09:27 AM, Waite, Dick (External) wrote: Grand Evening, This is what I see on an oldish Firefox that did down load the installer and packages for Beta3 on x86_64 and s390x.... So I think something is not quite right...with the SUMS, all three say Beat2... e3bbc395ff30f16bbba9e419244d8cd0 SLE-15-Installer-DVD-aarch64-Beta2-DVD1.iso 0dce5155cf6031f4ffb57a2b59430088 SLE-15-Installer-DVD-aarch64-Beta2-DVD2.iso 09fcadd42edebc9cd8c3fad3e8e454b5 SLE-15-Installer-DVD-aarch64-Beta2-DVD3.iso ... -- -- ... ________________________________________ From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Simon Flood [S.M.Flood at uis.cam.ac.uk] Sent: 27 November 2017 18:16 To: sle-beta at lists.suse.com Subject: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! On 27/11/17 17:08, Malcolm wrote: All very strange.... I've tried multiple systems with Firefox, including a private browsing window, refreshing etc. Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED 15 Beta3, SLES 12 SP3 and Windows 10. I've tried cleared cookies and history yet still only see the md5, sha1 and sha256 sums for beta 2..... Ditto, I'm also seeing Beta 2 *SUMS. Just tried Firefox private window on openSUSE Leap 42.2. Ditto. I just tried from a couple of different systems and three browsers here. (I'm 100% sure the Windows system using Internet Explorer has never hit the Beta download page before.) All system/browser combinations still have "SLE-15-*-Beta2-*.iso" checksums. - Don _______________________________________________ sle-beta mailing list sle-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From ext-linus.larsson at se.fujitsu.com Tue Nov 28 08:33:26 2017 From: ext-linus.larsson at se.fujitsu.com (ext-linus.larsson at se.fujitsu.com) Date: Tue, 28 Nov 2017 15:33:26 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <078513F0-176F-4D3B-9A1B-6A2A3AB99AD5@suse.com> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <1511785930185.57447@se.fujitsu.com>, <078513F0-176F-4D3B-9A1B-6A2A3AB99AD5@suse.com> Message-ID: <1511883206547.27941@se.fujitsu.com> Hi again, Sorry for the confusion, we use OBS with DoD (Download on demand) so we connect it to our local SMT mirror, so these packages are not available via SMT, how comes? /Linus ________________________________________ From: Vincent Moutoussamy Sent: Tuesday, November 28, 2017 14:24 To: Larsson, Linus Cc: sle-beta at lists.suse.com Subject: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! Hi, > On 27 Nov 2017, at 13:32, ext-linus.larsson at se.fujitsu.com wrote: > > Hi, > > When will support for building our own packages be fully added? Still missing at least these;? > post-build-checks In the Packages iso: Development-Tools-OBS/noarch/post-build-checks-84.87+git20170929.5b244d1-1.1.noarch.rpm > rpmlint-Factory In the Packages iso: Development-Tools-OBS/noarch/rpmlint-Factory-1.0-3.1.noarch.rpm > build-compare In the Packages iso: Development-Tools-OBS/noarch/build-compare-20171108T070456.b855319-1.1.noarch.rpm > brp-extract-appdata I didn?t find this one in our medias, but there is already a bug for it: https://bugzilla.suse.com/show_bug.cgi?id=1067645 Please make yourself in CC of this bug to be kept in touch about any advancement. > > Without them we can't build on OBS. > Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > > > From: sle-beta-bounces at lists.suse.com on behalf of SUSE Beta Program > Sent: Friday, November 24, 2017 17:37 > To: sle-beta at lists.suse.com > Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! > > Having trouble viewing this email? Please check the plain text version of it with your mailer. > Here comes Beta 3 of SUSE Linux Enterprise 15 for: > SUSE Linux Enterprise Server (SLES), > SUSE Linux Enterprise Desktop (SLED), > SUSE Linux Enterprise Workstation Extension (SLE-WE), > SUSE Linux Enterprise High Availablility (SLE-HA) > > Download ? Important Notice Online Channels for Beta 3At the time of this announcement, our SCC online channels synchronisations are still in progress. We expect them to finish in a few hours, in the mean time you need to use the SLE-15-Installer and SLE-15-Packages isos for your testing. > Migration from SLE 12 to SLE 15With Beta 3, we are still not in an ideal state for the support of the different migration scenarios from SLE 12 to SLE 15. You can try it but it is not expected to be smooth! Nevertheless do not hesitate to share your findings if you face any issues, but keep in mind that we are working on it. > Offline migration: With Beta 3, it is possible by using the SLE-15-Installer and SLE-15-Packages isos. > Online migration: Not possible with Beta 3, the SCC setup of the online channels still needs adaptation. We hope to get this done for future beta releases. > More information SLE Beta Page ? Release Notes ? Known Issues ? Your SUSE Linux Enterprise Team > Do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. > You received this email because you're signed up to get updates from us. Click here to unsubscribe. > > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta From Dick.Waite at softwareag.com Tue Nov 28 09:36:55 2017 From: Dick.Waite at softwareag.com (Waite, Dick (External)) Date: Tue, 28 Nov 2017 16:36:55 +0000 Subject: [sle-beta] Upgrade Beta3 - SDK Issues In-Reply-To: References: <46AC8C81C10B8C48820201DF2AE1D76D011F7080F6@daeexmbx1.eur.ad.sag>, Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D011F70FA38@daeexmbx1.eur.ad.sag> Many Thanks Jiri, I have "Updated" two SLES12-SP3 machines to SLES15 and they both look Okay at the moment. One did have to run a few edits to get back my root logon but otherwise grand. The good words of Jiri were the magic ones, I could see the SDK was "ready for delete" but one has to tell it "delete" ;o) So may thanks SUSE 4.12.14-4.2 looks good. The re-register ran Okay, I registered the Workstation Ext with the extra key, not sure if I now how "two" versions as I also registered "Desktop Productivity" in the non SCC round. I does seem to run the full SCC update again after the register, but one did put the modules down with the non-scc 1st round.... But better to have two then none...;o) Looking forward to Beta4, I'm off to do they day job for a few days. __R ________________________________________ From: Jiri Srain [jsrain at suse.cz] Sent: 28 November 2017 09:55 To: Waite, Dick (External); sle-beta at lists.suse.com Subject: Re: [sle-beta] Upgrade Beta3 - SDK Issues Hello Dick, the workaround for this scenario is: Enter the package selector, find the product (resp. its corresponding -release package) and mark it for deletion. Normally the package (and product) are selected for deleting by the dependency solver, which may result in accidental deleting of a product and this is why YaST warns you. When you select it explicitly for removal, YaST will treat it as your decision and accept it. Jiri On 27.11.2017 17:13, Waite, Dick (External) wrote: > Hi Jiri, > > Had a little time so I tried a simple QE machine. It was updated to SLES12-SP3 + today's UP and the reg_key removed. > > I get the issue with the SDK and from what I can see it is marked for delete. I have added a few screen shots in that area.... What should I do to be able to move forward ? > > __R > > ________________________________________ > From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com] on behalf of Jiri Srain [jsrain at suse.cz] > Sent: 27 November 2017 07:32 > To: sle-beta at lists.suse.com > Subject: Re: [sle-beta] Upgrade Beta3 > > Hello, > > there are two ways to upgrade SLES12 to SLES15 planned: > > 1. Using the repos from SCC. In this case, system needs to be registered > and the new repositories are delivered form SCC. This is not yet > implemented with Beta3 > > 2. Fully off-line (meaning no SCC, does not matter whether you use the > modules media or their local HTTP mirror), where you need to select > needed modules manually; however, this requires the system not to be > registered, because otherwise it ends up with mix of SLES12 and SLES15 > repositories. You can re-register the system after upgrade, though. > > HTH, > Jiri > > On 25.11.2017 02:33, Waite, Dick (External) wrote: >> I had a glass of Irish... >> >> SUSEConnect --cleanup to remove all registration trace. >> >> shutdown -r now >> >> upgrade >> >> as the words say, it's a big bumpy but along this track you do get into >> upgrade mode... Seems if the system knows it's registered it pop's off >> home... >> >> More in the morning, I'll let this update tonight. >> >> __R >> ------------------------------------------------------------------------ >> *From:* Waite, Dick (External) >> *Sent:* 25 November 2017 01:55 >> *To:* 'sle-beta at lists.suse.com' >> *Cc:* 'Vincent Moutoussamy' >> *Subject:* Upgrade Beta3 >> >> Grand Night, >> >> A new install ran Okay. >> >> I tried an offline migration using the installer and package: >> >> Finds the old version Okay then pops off to the SCC and you then get a >> "No migration product found". I tried with out a network and then I get >> an internal error. >> >> Need to stop it asking home about an update.... >> >> >> Migration from SLE 12 to SLE 15 >> >> With Beta 3, we are still not in an ideal state for the support of the >> different migration scenarios from SLE 12 to SLE 15. You can try it but >> it is not expected to be smooth! Nevertheless do not hesitate to share >> your findings if you face any issues, but keep in mind that we are >> working on it. >> >> * *Offline migration:* With Beta 3, it is possible by using the >> *SLE-15-Installer* and *SLE-15-Packages* isos. >> >> >> __R >> >> >> Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, >> Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - >> Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), >> Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - >> Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas >> Bereczky - *http://www.softwareag.com* >> >> >> >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta >> > > -- > Regards, > > Jiri Srain > Project Manager > --------------------------------------------------------------------- > SUSE LINUX, s.r.o. e-mail: jsrain at suse.com > Krizikova 148/34 tel: +420 284 084 659 > 186 00 Praha 8 fax: +420 284 084 001 > Czech Republic http://www.suse.com > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain at suse.com Krizikova 148/34 tel: +420 284 084 659 186 00 Praha 8 fax: +420 284 084 001 Czech Republic http://www.suse.com From vmoutoussamy at suse.com Wed Nov 29 03:03:42 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 29 Nov 2017 11:03:42 +0100 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> Message-ID: <7414C60D-4F14-4C09-8314-EF65538B57A0@suse.com> Hi, Our webteam told me that the CDN cache was purged and that should fix the issue. For those who faced the issue, could you please confirm that this is OK now? Starting with Beta 4, we might name our SUMS files: *SUMS.betaX to prevent this kind of issue from happening. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > On 28 Nov 2017, at 11:35, Vincent Moutoussamy > wrote: > > Hi, > > Ok so we definitely have a CDN issue for the SUMS files. > I will escalate this issue but in the mean time could you please: > - Tell us what?s current your location (city is enough)? > - Report the output of ?dig cdn.microfocus.com ? > > Thank you all and sorry for the inconvenience, > > Regards, > > PS: SUMS files for Beta3 are attached. > ? > Vincent Moutoussamy > SUSE Beta Program and SDK Project Manager > >> On 27 Nov 2017, at 18:46, Don Buchholz > wrote: >> >> On 11/27/2017 09:27 AM, Waite, Dick (External) wrote: >>> Grand Evening, >>> >>> This is what I see on an oldish Firefox that did down load the installer and packages for Beta3 on x86_64 and s390x.... So I think something is not quite right...with the SUMS, all three say Beat2... >>> >>> e3bbc395ff30f16bbba9e419244d8cd0 SLE-15-Installer-DVD-aarch64-Beta2-DVD1.iso >>> 0dce5155cf6031f4ffb57a2b59430088 SLE-15-Installer-DVD-aarch64-Beta2-DVD2.iso >>> 09fcadd42edebc9cd8c3fad3e8e454b5 SLE-15-Installer-DVD-aarch64-Beta2-DVD3.iso >>> ... -- -- ... >>> ________________________________________ >>> From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com ] on behalf of Simon Flood [S.M.Flood at uis.cam.ac.uk ] >>> Sent: 27 November 2017 18:16 >>> To: sle-beta at lists.suse.com >>> Subject: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! >>> >>> On 27/11/17 17:08, Malcolm wrote: >>> >>>> All very strange.... I've tried multiple systems with Firefox, including >>>> a private browsing window, refreshing etc. >>>> >>>> Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED >>>> 15 Beta3, SLES 12 SP3 and Windows 10. >>>> >>>> I've tried cleared cookies and history yet still only see the md5, sha1 >>>> and sha256 sums for beta 2..... >>> Ditto, I'm also seeing Beta 2 *SUMS. Just tried Firefox private window >>> on openSUSE Leap 42.2. >>> >> >> Ditto. I just tried from a couple of different systems and three browsers here. (I'm 100% sure the Windows system using Internet Explorer has never hit the Beta download page before.) All system/browser combinations still have "SLE-15-*-Beta2-*.iso" checksums. >> >> - Don >> >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta > > > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From S.M.Flood at uis.cam.ac.uk Wed Nov 29 05:09:23 2017 From: S.M.Flood at uis.cam.ac.uk (Simon Flood) Date: Wed, 29 Nov 2017 12:09:23 +0000 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: <7414C60D-4F14-4C09-8314-EF65538B57A0@suse.com> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> <7414C60D-4F14-4C09-8314-EF65538B57A0@suse.com> Message-ID: Hi Vincent, Sorry but whatever I do (change browser, clear caches, etc.) I'm still getting the Beta 2 versions of *SUMS. HTH, Simon On 29/11/17 10:03, Vincent Moutoussamy wrote: > Hi, > > Our webteam told me that the CDN cache was purged and that should fix the issue. > > For those who faced the issue, could you please confirm that this is OK now? > > Starting with Beta 4, we might name our SUMS files: *SUMS.betaX to prevent this > kind of issue from happening. > > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program and SDK Project Manager > >> On 28 Nov 2017, at 11:35, Vincent Moutoussamy > wrote: >> >> Hi, >> >> Ok so we definitely have a CDN issue for the SUMS files. >> I will escalate this issue but in the mean time could you please: >> - Tell us what?s current your location (city is enough)? >> - Report the output of ?dig cdn.microfocus.com ? >> >> Thank you all and sorry for the inconvenience, >> >> Regards, >> >> PS: SUMS files for Beta3 are attached. >> ? >> Vincent Moutoussamy >> SUSE Beta Program and SDK Project Manager >> >>> On 27 Nov 2017, at 18:46, Don Buchholz > wrote: >>> >>> On 11/27/2017 09:27 AM, Waite, Dick (External) wrote: >>>> Grand Evening, >>>> >>>> This is what I see on an oldish Firefox that did down load the installer and packages for Beta3 on x86_64 and s390x.... So I think something is not quite right...with the SUMS, all three say Beat2... >>>> >>>> e3bbc395ff30f16bbba9e419244d8cd0 SLE-15-Installer-DVD-aarch64-Beta2-DVD1.iso >>>> 0dce5155cf6031f4ffb57a2b59430088 SLE-15-Installer-DVD-aarch64-Beta2-DVD2.iso >>>> 09fcadd42edebc9cd8c3fad3e8e454b5 SLE-15-Installer-DVD-aarch64-Beta2-DVD3.iso >>>> ... -- -- ... >>>> ________________________________________ >>>> From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com ] on behalf of Simon Flood [S.M.Flood at uis.cam.ac.uk ] >>>> Sent: 27 November 2017 18:16 >>>> To: sle-beta at lists.suse.com >>>> Subject: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! >>>> >>>> On 27/11/17 17:08, Malcolm wrote: >>>> >>>>> All very strange.... I've tried multiple systems with Firefox, including >>>>> a private browsing window, refreshing etc. >>>>> >>>>> Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED >>>>> 15 Beta3, SLES 12 SP3 and Windows 10. >>>>> >>>>> I've tried cleared cookies and history yet still only see the md5, sha1 >>>>> and sha256 sums for beta 2..... >>>> Ditto, I'm also seeing Beta 2 *SUMS. Just tried Firefox private window >>>> on openSUSE Leap 42.2. >>>> >>> >>> Ditto. I just tried from a couple of different systems and three browsers here. (I'm 100% sure the Windows system using Internet Explorer has never hit the Beta download page before.) All system/browser combinations still have "SLE-15-*-Beta2-*.iso" checksums. >>> >>> - Don >>> >>> _______________________________________________ >>> sle-beta mailing list >>> sle-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/sle-beta >> >> >> >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta > > > > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta > -- Simon Flood HPC System Administrator University of Cambridge Information Services United Kingdom SUSE Knowledge Partner From vmoutoussamy at suse.com Wed Nov 29 05:19:51 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 29 Nov 2017 13:19:51 +0100 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! In-Reply-To: References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> <7414C60D-4F14-4C09-8314-EF65538B57A0@suse.com> Message-ID: Hi, > On 29 Nov 2017, at 13:09, Simon Flood wrote: > > Hi Vincent, > > Sorry but whatever I do (change browser, clear caches, etc.) I'm still getting the Beta 2 versions of *SUMS. Well don?t be sorry, we are the one who should be. Thanks for the heads-up, I will forward this to our web team and CDN provider. As workaround for SLE15, I will now upload MD5SUMS.beta3, SHA1SUMS.beta3 and SHA256SUMS.beta3 in the download page. Sorry for the inconvenience, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager > HTH, > Simon > > On 29/11/17 10:03, Vincent Moutoussamy wrote: >> Hi, >> Our webteam told me that the CDN cache was purged and that should fix the issue. >> For those who faced the issue, could you please confirm that this is OK now? >> Starting with Beta 4, we might name our SUMS files: *SUMS.betaX to prevent this >> kind of issue from happening. >> Regards, >> -- >> Vincent Moutoussamy >> SUSE Beta Program and SDK Project Manager >>> On 28 Nov 2017, at 11:35, Vincent Moutoussamy > wrote: >>> >>> Hi, >>> >>> Ok so we definitely have a CDN issue for the SUMS files. >>> I will escalate this issue but in the mean time could you please: >>> - Tell us what?s current your location (city is enough)? >>> - Report the output of ?dig cdn.microfocus.com ? >>> >>> Thank you all and sorry for the inconvenience, >>> >>> Regards, >>> >>> PS: SUMS files for Beta3 are attached. >>> ? >>> Vincent Moutoussamy >>> SUSE Beta Program and SDK Project Manager >>> >>>> On 27 Nov 2017, at 18:46, Don Buchholz > wrote: >>>> >>>> On 11/27/2017 09:27 AM, Waite, Dick (External) wrote: >>>>> Grand Evening, >>>>> >>>>> This is what I see on an oldish Firefox that did down load the installer and packages for Beta3 on x86_64 and s390x.... So I think something is not quite right...with the SUMS, all three say Beat2... >>>>> >>>>> e3bbc395ff30f16bbba9e419244d8cd0 SLE-15-Installer-DVD-aarch64-Beta2-DVD1.iso >>>>> 0dce5155cf6031f4ffb57a2b59430088 SLE-15-Installer-DVD-aarch64-Beta2-DVD2.iso >>>>> 09fcadd42edebc9cd8c3fad3e8e454b5 SLE-15-Installer-DVD-aarch64-Beta2-DVD3.iso >>>>> ... -- -- ... >>>>> ________________________________________ >>>>> From: sle-beta-bounces at lists.suse.com [sle-beta-bounces at lists.suse.com ] on behalf of Simon Flood [S.M.Flood at uis.cam.ac.uk ] >>>>> Sent: 27 November 2017 18:16 >>>>> To: sle-beta at lists.suse.com >>>>> Subject: Re: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 is now Beta 3! >>>>> >>>>> On 27/11/17 17:08, Malcolm wrote: >>>>> >>>>>> All very strange.... I've tried multiple systems with Firefox, including >>>>>> a private browsing window, refreshing etc. >>>>>> >>>>>> Operating systems tried: openSUSE leap 42.2, Tumbleweed 20171125, SLED >>>>>> 15 Beta3, SLES 12 SP3 and Windows 10. >>>>>> >>>>>> I've tried cleared cookies and history yet still only see the md5, sha1 >>>>>> and sha256 sums for beta 2..... >>>>> Ditto, I'm also seeing Beta 2 *SUMS. Just tried Firefox private window >>>>> on openSUSE Leap 42.2. >>>>> >>>> >>>> Ditto. I just tried from a couple of different systems and three browsers here. (I'm 100% sure the Windows system using Internet Explorer has never hit the Beta download page before.) All system/browser combinations still have "SLE-15-*-Beta2-*.iso" checksums. >>>> >>>> - Don >>>> >>>> _______________________________________________ >>>> sle-beta mailing list >>>> sle-beta at lists.suse.com >>>> http://lists.suse.com/mailman/listinfo/sle-beta >>> >>> >>> >>> _______________________________________________ >>> sle-beta mailing list >>> sle-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/sle-beta >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta > > -- > Simon Flood > HPC System Administrator > University of Cambridge Information Services > United Kingdom > > SUSE Knowledge Partner > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From jrd at netlab1.net Wed Nov 29 07:51:03 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Wed, 29 Nov 2017 14:51:03 +0000 Subject: [sle-beta] Beta 3, no Gnome In-Reply-To: <20171128060423.0e0c7b67@grover.homelinux.org> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D011F70F7E1@daeexmbx1.eur.ad.sag> <20171128060423.0e0c7b67@grover.homelinux.org> Message-ID: <65f0ee44-2636-925b-4031-ee4c895db462@netlab1.net> ??? I seem to be caught in a snare on beta 3 Server. The problem is obtaining Gnome. ??? Last week I discussed SSL version problems in beta 3 and the test machine has Gnome running fine. This week I am diagnosing the SSL aspect and building now shows no graphical login choice. That is, during installation a Systems Role screen appears. It now shows Text Mode, Minimal, KVM, ZEN, but nothing else. There is no Gnome in the YaST software menu either, the Graphical Environments section shows only Fonts and X Window System . Try as I might, nothing improves this situation. ??? Installation is as a regular VMware ESXi v6 virtual machine. I have tried all the video mode selection values on the boot screen, including "default" and telling the boot kernel "nomodeset" and the situation does not change. Normally I select 1024x768 as that has worked fine on all the many SUSE based virtual machines here for years. ??? I have tried not choosing repositories, and the Roles screen shows only Minimal. If I disconnect the network and start an install then again the Roles screen shows only Miminal. This reduction in capabilities is definitely not good. The installation media alone ought to have what it takes to build a regular GUI based server, no frills, and apparently in beta 3 that is not the case (which is a strange situation). ??? At installation time I also see the system try to reach SUSE and update the installer, without my permission. That is also an unwise step, breaking confidence in the DVD material to do the installation job and adding unknown things at the very start. I have no trust in such remote fetch actions. I suggest either skipping that update step or requiring the user's permission to do it. ??? Don't ask why I got away with this last week. I must have been very bad over the weekend to deserve this treatment. ??? Thanks, ??? Joe D. From fcrozat at suse.com Wed Nov 29 09:15:14 2017 From: fcrozat at suse.com (Frederic Crozat) Date: Wed, 29 Nov 2017 17:15:14 +0100 Subject: [sle-beta] Beta 3, no Gnome In-Reply-To: <65f0ee44-2636-925b-4031-ee4c895db462@netlab1.net> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D011F70F7E1@daeexmbx1.eur.ad.sag> <20171128060423.0e0c7b67@grover.homelinux.org> <65f0ee44-2636-925b-4031-ee4c895db462@netlab1.net> Message-ID: <1511972114.16667.54.camel@suse.com> Le mercredi 29 novembre 2017 ? 14:51 +0000, Joe Doupnik a ?crit?: > ???? I seem to be caught in a snare on beta 3 Server. The problem is? > obtaining Gnome. > ???? Last week I discussed SSL version problems in beta 3 and the > test? > machine has Gnome running fine. This week I am diagnosing the SSL > aspect? > and building now shows no graphical login choice. That is, during? > installation a Systems Role screen appears. It now shows Text Mode,? > Minimal, KVM, ZEN, but nothing else. There is no Gnome in the YaST? > software menu either, the Graphical Environments section shows only? > Fonts and X Window System . You didn't add the "Desktop Application" module when registering to SCC (or when using the Packages iso). -- Frederic Crozat Enterprise Desktop Release Manager SUSE From vmoutoussamy at suse.com Wed Nov 29 09:34:11 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 29 Nov 2017 17:34:11 +0100 Subject: [sle-beta] General advice about email threading in beta mailing list Message-ID: Hi, Please avoid to ?respond? on another sle-beta emails to create a new topic. Because this cause the addition of your new topic in the former email thread, which will affect our sle-beta archives (http://lists.suse.com/pipermail/sle-beta/2017-November/thread.html) and also others members email thread in their favorite email client. By creating a ?new thread?, this can help you to have more attention to your new topic from SUSE employees and other beta participants. Kind regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From jrd at netlab1.net Wed Nov 29 09:54:42 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Wed, 29 Nov 2017 16:54:42 +0000 Subject: [sle-beta] Beta 3, no Gnome In-Reply-To: <1511972114.16667.54.camel@suse.com> References: <5a184ad6a143f_1a025dd3247222a@boucane.mail> <20171124110235.68cdf342@grover.homelinux.org> <20171125104303.48e9c5da@grover.homelinux.org> <9FEBA363-DFE6-40A4-8BEB-CE5A21C752EF@suse.com> <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D011F70F7E1@daeexmbx1.eur.ad.sag> <20171128060423.0e0c7b67@grover.homelinux.org> <65f0ee44-2636-925b-4031-ee4c895db462@netlab1.net> <1511972114.16667.54.camel@suse.com> Message-ID: <1d0bf589-c041-1d8e-288c-bd6eb9f1cd43@netlab1.net> On 29/11/2017 16:15, Frederic Crozat wrote: > Le mercredi 29 novembre 2017 ? 14:51 +0000, Joe Doupnik a ?crit?: >> ???? I seem to be caught in a snare on beta 3 Server. The problem is >> obtaining Gnome. >> ???? Last week I discussed SSL version problems in beta 3 and the >> test >> machine has Gnome running fine. This week I am diagnosing the SSL >> aspect >> and building now shows no graphical login choice. That is, during >> installation a Systems Role screen appears. It now shows Text Mode, >> Minimal, KVM, ZEN, but nothing else. There is no Gnome in the YaST >> software menu either, the Graphical Environments section shows only >> Fonts and X Window System . > You didn't add the "Desktop Application" module when registering to SCC > (or when using the Packages iso). > ------------- ??? Correct, I did not because I am installing a server, not the desktop product line. ??? With your suggestion, I have just done a new installation, ticking the desktop applications box for this server, and finally the Gnome option appears in System Role. Opaque. ??? A couple of obvious comments here. ??? First, GUIs are rather common on servers. Hiding them at the very outset under a seemingly unrelated label (desktop) is not helpful. ??? Second, restricting software choices to just someone's bright ideas about Roles is not satisfactory. I don't know those details or may not agree with them. A full selection needs to be shown where possible, not hampered by a "helpful" canned approach. Make such Roles selection be optional, helpful, not mandatory, returning to its original goal of being an offered convenience where such pre-selection does not produce restriction or invisibility. Yes, this is mixed with the over-division of software which is occurring presently, so some rethinking about actual benefits to end users of those silos could be useful. ??? I know that my machines will disagree with me when I say that I control them rather than vice versa, though I do try, and I rather wish to not add a remote third party's opaque restrictions to the choosing process. ??? Thanks, ??? Joe D. From mmarion at qualcomm.com Wed Nov 29 10:05:31 2017 From: mmarion at qualcomm.com (Mike Marion) Date: Wed, 29 Nov 2017 17:05:31 +0000 Subject: [sle-beta] Beta 3, no Gnome In-Reply-To: <1d0bf589-c041-1d8e-288c-bd6eb9f1cd43@netlab1.net> References: <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D011F70F7E1@daeexmbx1.eur.ad.sag> <20171128060423.0e0c7b67@grover.homelinux.org> <65f0ee44-2636-925b-4031-ee4c895db462@netlab1.net> <1511972114.16667.54.camel@suse.com> <1d0bf589-c041-1d8e-288c-bd6eb9f1cd43@netlab1.net> Message-ID: <20171129170530.GG2873@qualcomm.com> On Wed, Nov 29, 2017 at 04:54:42PM +0000, Joe Doupnik wrote: > ??? Correct, I did not because I am installing a server, not the > desktop product line. > ??? With your suggestion, I have just done a new installation, ticking > the desktop applications box for this server, and finally the Gnome > option appears in System Role. Opaque. I actually find this split with SLE15 a lot clearer than the current SLES vs SLED or SLES+WE. I take this move as a sign that Suse also seems to realize that the current split between SLES and SLED probably should go away (despite there still being SLES and SLED offered). As you mention, most of the time the difference seems to be based on arbitrary decisions. Don't get me started on how support for SLED vs SLES is done despite them being the same code base. -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com From jrd at netlab1.net Wed Nov 29 12:21:27 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Wed, 29 Nov 2017 19:21:27 +0000 Subject: [sle-beta] Beta3 post install software installation In-Reply-To: <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> Message-ID: <845d2b2d-3686-b5f5-5d29-7ab7168ab06a@netlab1.net> ??? Here is a quick and only preliminary report about the SSL problem which I reported a few days ago (included below). ??? Two Beta 3 servers were built. One having OpenSSL v1.1 added and experiencing problems, the second working. ??? Inspection of /usr/lib64/libssl* shows the first (problem) server has "libssl.so" symlinked to libssl.so.1.1. On the second server the symlink is to libssl.so.1.0.0. Moments ago I manually shifted the symlink on the first server to libssl.so.1.0.0 (which is present), rebooted the machine, and did a quick zypper lu command. That failed with the certificate errors. On the first machine zipper lu does work. ??? Next I visited /etc/ssl on both machines. On the first, as noted below, it was basically empty. On the second there are entries ca-bundle.pem (which ought not appear there), certs (symlinked to /var/lib/ca-certificates/pem, which is a mess), and private (empty). This is markedly different than on previous SLES editions, and it is a bit of a shambles. ??? On my main SLES11 server I have Openssl v0.9.8 and v1.0.1g, and both cohabit peacefully. I add or remove the -devel rpm to support the proper kind when building apps. ??? What I deduce thus far is asking to have Openssl v1.1 cohabit with v1.0.2 results in moving the main library symlink (libssl.so) to? v1.1 (which is not what I asked it to do), and the installation process became confused and decided to not even create the certificate store (even if in that wrong place of /var/lib for gosh sakes). No certs, no service, as we might say. Populating the "private" directory with my formal certs failed with a no CA Cert error popup which we can now understand that from the flinging of what was in /etc/ssl/certs? into instead the distant /var/lib swamp (so, if doing that then why bother with having an /etc/ssl directory?). ??? In my view, the /etc/ssl construction prior to SLES15 is superior, clear, manageable, and what we have wired into our applications. Putting things in /var/lib is not good. Then, relying on (changing) symlinks in /etc/ssl is to further confuse an important area.? The YaST/installation part of things needs attention. The prior construction of /etc/ssl is organized for managers of the machines, and /var/lib is a large collecting ground for much other "stuff." I recommend we return to the safe and sane way of storing certificates. ??? Thanks, ??? Joe D. On 26/11/2017 16:04, Joe Doupnik wrote: > ??? I have run into two problems just after installation of beta 3. > ??? If I ask YaST to allow me to inspect and install further software > then the process blocks with a popup which reduces to curl being > unable to find the local issuer's SSL certificate, curl error 60. The > repositories are those on SUSE, straight from the installation process. > ??? Directory /etc/ssl/private is empty, thus no self signed certs. > Adding my proper certs into /etc/ssl/servercerts, and symlinking > /etc/ssl/private to that same directory has not improved things. Then > looking more carefully at /etc/ssl I find a large vacuum where CA > certs ought to be, empty space populated by only a lonely file named > openssl.cnf. > ??? Taking a space walk into that problem, I went into YaST | > Software, asked about "certificate", got a list of installed > candidates, chose ca-certificates, got a warning popup which says I > must uninstall openssl v1.1 and install v1.0.2l. Hmmm, I had thought > certificates were impervious to editions of openssl, being rather > separate operations, but now we see them glued together. Not what I > expected nor can use. > ??? Not to be stopped by mere failures, I told YaST to use option 3, > break dependencies for the ca-certificates item. It responded with an > error popup which said it could not contact SUSE to do this chore. At > this point I have that "Catch-22" feeling. It starts with certificates > being absent, and matters slide downhill from there. > ??? What might be acting in this case is I have selected to install > OpenSSL v1.1 rather than the default v1.0.2. The SSL selection part > also indicates awkwardness which needs attention. That is, YaST does > not wish to allow me to install the SSL libraries for both versions of > SSL, even though the libraries do cohabit on earlier SLES's. My normal > drill is install two libraries, then when building things install the > appropriate -devel version so that the desired SSL version headers are > used. > ??? Tis a puzzle at this moment. > ??? Thanks, > ??? Joe D. > > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta From jrd at netlab1.net Wed Nov 29 12:55:41 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Wed, 29 Nov 2017 19:55:41 +0000 Subject: [sle-beta] Beta3 post install software installation In-Reply-To: <845d2b2d-3686-b5f5-5d29-7ab7168ab06a@netlab1.net> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> <845d2b2d-3686-b5f5-5d29-7ab7168ab06a@netlab1.net> Message-ID: <57534436-73a7-e5bf-e38c-9e26d2371a4d@netlab1.net> ??? Addendum to the msg below, dealing with YaST this time. ??? On the "second" machine built without adjustments, after taking a VMware snapshot I have asked YaST to install Openssl v1.1. Selecting just libopenssl1_1_0 worked, but while there adding either (or both) openssl-1_1_0 or libopenssl-1_1_0-devel produces a conflict message from YaST where it requires one to remove the present v1.0.2l files and remove pesign-obs-integration. That's the part of the problem. ??? YaST should allow libopenssl1_1_0 to enter without complaint as there is no conflict. When the -devel material is added then it should offer to remove only the existing/conflicting -devel RPM. That way one can flip flop -devel's to build as desired. Futzing with the libssl.so symlink is another weak link in the chain and that should be handled more gracefully than at present. ??? Thus at this moment in affairs openssl v1.1 is a no-go item in SLES. Golly, we need a Security channel again to have selected apps which are built for v1.1. Right, just what you wanted to hear. Sorry about that. ??? Thanks, ??? Joe D. On 29/11/2017 19:21, Joe Doupnik wrote: > Here is a quick and only preliminary report about the SSL problem > which I reported a few days ago (included below). > ??? Two Beta 3 servers were built. One having OpenSSL v1.1 added and > experiencing problems, the second working. > ??? Inspection of /usr/lib64/libssl* shows the first (problem) server > has "libssl.so" symlinked to libssl.so.1.1. On the second server the > symlink is to libssl.so.1.0.0. Moments ago I manually shifted the > symlink on the first server to libssl.so.1.0.0 (which is present), > rebooted the machine, and did a quick zypper lu command. That failed > with the certificate errors. On the first machine zipper lu does work. > ??? Next I visited /etc/ssl on both machines. On the first, as noted > below, it was basically empty. On the second there are entries > ca-bundle.pem (which ought not appear there), certs (symlinked to > /var/lib/ca-certificates/pem, which is a mess), and private (empty). > This is markedly different than on previous SLES editions, and it is a > bit of a shambles. > ??? On my main SLES11 server I have Openssl v0.9.8 and v1.0.1g, and > both cohabit peacefully. I add or remove the -devel rpm to support the > proper kind when building apps. > ??? What I deduce thus far is asking to have Openssl v1.1 cohabit with > v1.0.2 results in moving the main library symlink (libssl.so) to? v1.1 > (which is not what I asked it to do), and the installation process > became confused and decided to not even create the certificate store > (even if in that wrong place of /var/lib for gosh sakes). No certs, no > service, as we might say. Populating the "private" directory with my > formal certs failed with a no CA Cert error popup which we can now > understand that from the flinging of what was in /etc/ssl/certs? into > instead the distant /var/lib swamp (so, if doing that then why bother > with having an /etc/ssl directory?). > ??? In my view, the /etc/ssl construction prior to SLES15 is superior, > clear, manageable, and what we have wired into our applications. > Putting things in /var/lib is not good. Then, relying on (changing) > symlinks in /etc/ssl is to further confuse an important area.? The > YaST/installation part of things needs attention. The prior > construction of /etc/ssl is organized for managers of the machines, > and /var/lib is a large collecting ground for much other "stuff." I > recommend we return to the safe and sane way of storing certificates. > ??? Thanks, > ??? Joe D. > > > On 26/11/2017 16:04, Joe Doupnik wrote: >> ??? I have run into two problems just after installation of beta 3. >> ??? If I ask YaST to allow me to inspect and install further software >> then the process blocks with a popup which reduces to curl being >> unable to find the local issuer's SSL certificate, curl error 60. The >> repositories are those on SUSE, straight from the installation process. >> ??? Directory /etc/ssl/private is empty, thus no self signed certs. >> Adding my proper certs into /etc/ssl/servercerts, and symlinking >> /etc/ssl/private to that same directory has not improved things. Then >> looking more carefully at /etc/ssl I find a large vacuum where CA >> certs ought to be, empty space populated by only a lonely file named >> openssl.cnf. >> ??? Taking a space walk into that problem, I went into YaST | >> Software, asked about "certificate", got a list of installed >> candidates, chose ca-certificates, got a warning popup which says I >> must uninstall openssl v1.1 and install v1.0.2l. Hmmm, I had thought >> certificates were impervious to editions of openssl, being rather >> separate operations, but now we see them glued together. Not what I >> expected nor can use. >> ??? Not to be stopped by mere failures, I told YaST to use option 3, >> break dependencies for the ca-certificates item. It responded with an >> error popup which said it could not contact SUSE to do this chore. At >> this point I have that "Catch-22" feeling. It starts with >> certificates being absent, and matters slide downhill from there. >> ??? What might be acting in this case is I have selected to install >> OpenSSL v1.1 rather than the default v1.0.2. The SSL selection part >> also indicates awkwardness which needs attention. That is, YaST does >> not wish to allow me to install the SSL libraries for both versions >> of SSL, even though the libraries do cohabit on earlier SLES's. My >> normal drill is install two libraries, then when building things >> install the appropriate -devel version so that the desired SSL >> version headers are used. >> ??? Tis a puzzle at this moment. >> ??? Thanks, >> ??? Joe D. >> >> >> _______________________________________________ >> sle-beta mailing list >> sle-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sle-beta > > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sle-beta From kukuk at suse.de Wed Nov 29 14:01:06 2017 From: kukuk at suse.de (Thorsten Kukuk) Date: Wed, 29 Nov 2017 22:01:06 +0100 Subject: [sle-beta] Beta3 post install software installation In-Reply-To: <845d2b2d-3686-b5f5-5d29-7ab7168ab06a@netlab1.net> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> <845d2b2d-3686-b5f5-5d29-7ab7168ab06a@netlab1.net> Message-ID: <20171129210106.GA4741@suse.de> On Wed, Nov 29, Joe Doupnik wrote: > ??? In my view, the /etc/ssl construction prior to SLES15 is superior, > clear, manageable, and what we have wired into our applications. How can the /etc/ssl construct prior to SLES15 be superior if it is identical between SLES12 and SLES15? Maybe you should start at first in your bug reports with what you are exactly doing and what the exact error messages are? Beside that it is not working on one machine for you, there is not much we can use to identify the root cause. Start for example with the error message of update-ca-certifiates. Beside that, if changing the libssl.so symlink makes a different for you, that you have some broken third party RPMs flying around somewhere. libssl.so is only used for linking applications, it should never be needed at runtime. If you have applications which needs this link at runtime, you have lost. This will never work stable. And libssl.so is coming with a *-devel RPM. And the *.so symlink has to match exactly the header files, else compiling and linking will never work, too. If you have the wrong *-devel package installed, you should deinstall it and install the right one, not changing symlinks. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From vmoutoussamy at suse.com Thu Nov 30 03:32:33 2017 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 30 Nov 2017 11:32:33 +0100 Subject: [sle-beta] Beta 3, no Gnome In-Reply-To: <20171129170530.GG2873@qualcomm.com> References: <20171127110853.6fe8077c@grover.homelinux.org> <301387bc-0259-94e3-ea43-14bc16a2206f@uis.cam.ac.uk> <46AC8C81C10B8C48820201DF2AE1D76D011F7091BE@daeexmbx1.eur.ad.sag> <30e4bfe1-37c3-a34c-d18a-815da0eb8712@intel.com> <79E54318-FBCF-4611-8C47-E395D4BCF13F@suse.com> <46AC8C81C10B8C48820201DF2AE1D76D011F70F7E1@daeexmbx1.eur.ad.sag> <20171128060423.0e0c7b67@grover.homelinux.org> <65f0ee44-2636-925b-4031-ee4c895db462@netlab1.net> <1511972114.16667.54.camel@suse.com> <1d0bf589-c041-1d8e-288c-bd6eb9f1cd43@netlab1.net> <20171129170530.GG2873@qualcomm.com> Message-ID: <71006C17-8FBF-41DF-8A90-9BA32C951ED7@suse.com> Hi, > On 29 Nov 2017, at 18:05, Mike Marion wrote: > > On Wed, Nov 29, 2017 at 04:54:42PM +0000, Joe Doupnik wrote: > >> Correct, I did not because I am installing a server, not the >> desktop product line. >> With your suggestion, I have just done a new installation, ticking >> the desktop applications box for this server, and finally the Gnome >> option appears in System Role. Opaque. > > I actually find this split with SLE15 a lot clearer than the current > SLES vs SLED or SLES+WE. > > I take this move as a sign that Suse also seems to realize that the > current split between SLES and SLED probably should go away (despite > there still being SLES and SLED offered). As you mention, most of the > time the difference seems to be based on arbitrary decisions. Don't get > me started on how support for SLED vs SLES is done despite them being > the same code base. Well if you have unanswered technical question, please ask them here (but let?s create a new thread). If you have unfulfilled needs for your own use case for SLED, SLES, SLE-WE, we can also discuss this privately via beta-programs at lists.suse.com. Last but not least, it is true that all SLE products have the same code base, but the devil is in the details, they do not have the same use cases, nor used with the same hardware (GPU, display, etc) and they also bring their own packages which are not present in other SLE products. That?s the general reason why SLED and SLES have different support policy. Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From jrd at netlab1.net Thu Nov 30 03:47:56 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Thu, 30 Nov 2017 10:47:56 +0000 Subject: [sle-beta] Beta3 post install software installation In-Reply-To: <20171129210106.GA4741@suse.de> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> <845d2b2d-3686-b5f5-5d29-7ab7168ab06a@netlab1.net> <20171129210106.GA4741@suse.de> Message-ID: Thorsten and the group, ??? Fair enough. What I am trying to do in this particular case is use Openssl v1.1 to support building an application, and see if existing apps could use it. The answer to the latter is typically no, of course, as they are built against v1.0.2, which is a situation similar to using the Security Channel of previous versions of SLES to supply a few key apps built with another version of SSL. Building my own code needs SSL v1.1 for checking matters, and that means both the library and the headers (-devel bundle). ? Where matters become sticky is adding the -devel material, where YaST decides that we must remove all of the earlier SSL material (thus the earlier library as well). I think that is a step too far in the dependency resolution problem, where there is conflict only about the -devel part. This seems to be readily curable by a script tweak or two. ??? So far, the running of apps is indeed supported by symlink libssl.so and we can install multiple libssl's. I point the symlink at an active library. Building an application with other than the stock SSL runs into difficulties because adding a more recent SSL -devel part causes wider spread trouble. ??? Next there are the certificates. Right now this seems to be a muddle. I have two Beta 3 machines set up, one with the choice of SSL v1.1 and the second with the stock SSL v1.0.x. The first has experienced the discussed problems, and the second does work reasonably well. The certificate blockage does seem to be a dependency criteria which I have not decoded. ??? Here is a screen capture of one case: on the SSL v1.1 (first) machine.? In YaST ask to install the ca-certificates RPM material, and the conflict resolution screen shown below appears: ??? It says that to obtain the CA cert material I also must remove SSL v1.1, for unknown reasons. The best that I can guess is there is some hidden agent which is built against SSL v1.0.x which wants to be a guardian of such certs and can't work with SSL v1.1.? Just where I would place my regular cert material is uncertain as there is no corresponding area in either /etc/ssl nor /var/lib. Note that for this report's tests I have pointed the libssl.so symlink at the SSL v1.0.x library, thusly: Note the date stamp on that symlink as it shows I modified it yesterday for this test. ??? Next, the software update error messages on the SSL v1.1 machine. Four screen captures. ??? The first is visiting YaST Online Update: ??? Skipping the Autorefresh produces this curl error 60 popup: ??? Then if one issues command?? zypper lu? the screen shows many lines such as this one: or the same but in a terminal session in the GUI: All are saying the CA cert is not available, which we know from the CA problem above, and indeed there is no CA cert area. ??? From my vantage a couple of comments. ??? First, have the usual CA bundle be present/installable, regardless of OpenSSL versions. That takes some detective work at the SUSE end to resolve. Then Curl, Apache, zypper et al would stand a chance of running against at minimum a self signed cert or more normally against a user supplied set. Swapping a symlink for development is the manager's choice. ??? Second, the /etc/ssl grouping of cert material makes good sense. This goes against the unfortunate LSB grain of scattering things all over. The reason is to get at the certificate material (as we must these days) in a simple easy to remember fashion and avoid being tripped up by symlinks hiding elsewhere. It's usage in the field which is important, a people and management time concern. ??? Thanks, ??? Joe D. On 29/11/2017 21:01, Thorsten Kukuk wrote: > On Wed, Nov 29, Joe Doupnik wrote: > >> ??? In my view, the /etc/ssl construction prior to SLES15 is superior, >> clear, manageable, and what we have wired into our applications. > How can the /etc/ssl construct prior to SLES15 be superior if it is > identical between SLES12 and SLES15? > > Maybe you should start at first in your bug reports with what you are > exactly doing and what the exact error messages are? Beside that it is > not working on one machine for you, there is not much we can use to > identify the root cause. > Start for example with the error message of update-ca-certifiates. > > Beside that, if changing the libssl.so symlink makes a different for you, > that you have some broken third party RPMs flying around somewhere. > libssl.so is only used for linking applications, it should never be > needed at runtime. If you have applications which needs this link at > runtime, you have lost. This will never work stable. > And libssl.so is coming with a *-devel RPM. And the *.so symlink has > to match exactly the header files, else compiling and linking will > never work, too. If you have the wrong *-devel package installed, > you should deinstall it and install the right one, not changing > symlinks. > > Thorsten > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jhmfcdkkfgbdjdae.png Type: image/png Size: 92119 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cgjiadnccjlmeloo.png Type: image/png Size: 18939 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pggnlmpbgkopfjka.png Type: image/png Size: 86713 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ghjikemaahkcddkm.png Type: image/png Size: 26439 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pfnmldjnhobdiife.png Type: image/png Size: 33587 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jeaopfgmbejchand.png Type: image/png Size: 111122 bytes Desc: not available URL: From kukuk at suse.de Thu Nov 30 04:50:59 2017 From: kukuk at suse.de (Thorsten Kukuk) Date: Thu, 30 Nov 2017 12:50:59 +0100 Subject: [sle-beta] Beta3 post install software installation In-Reply-To: References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> <845d2b2d-3686-b5f5-5d29-7ab7168ab06a@netlab1.net> <20171129210106.GA4741@suse.de> Message-ID: <20171130115059.GA3869@suse.de> Hi, On Thu, Nov 30, Joe Doupnik wrote: > Thorsten and the group, > ??? Fair enough. What I am trying to do in this particular case is use > Openssl v1.1 to support building an application, and see if existing apps > could use it. The answer to the latter is typically no, of course, as they > are built against v1.0.2, which is a situation similar to using the Security > Channel of previous versions of SLES to supply a few key apps built with > another version of SSL. Building my own code needs SSL v1.1 for checking > matters, and that means both the library and the headers (-devel bundle). > ? Where matters become sticky is adding the -devel material, where YaST > decides that we must remove all of the earlier SSL material (thus the > earlier library as well). I think that is a step too far in the dependency > resolution problem, where there is conflict only about the -devel part. This > seems to be readily curable by a script tweak or two. Yes, it is currently not possible to install openssl v1.1 and v1.0 in parallel, but this is what you need here. I hope our security team will find a solution for this. > ??? Next there are the certificates. Right now this seems to be a muddle. I > have two Beta 3 machines set up, one with the choice of SSL v1.1 and the > second with the stock SSL v1.0.x. The first has experienced the discussed > problems, and the second does work reasonably well. The certificate blockage > does seem to be a dependency criteria which I have not decoded. > ??? Here is a screen capture of one case: on the SSL v1.1 (first) machine.? > In YaST ask to install the ca-certificates RPM material, and the conflict > resolution screen shown below appears: That's a similar problem: YaST/zypper always tries to install the newest version. You have to select the openssl-1.0 package manually. But the question is: why is ca-certificates not installed? Should always be installed. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) From jrd at netlab1.net Thu Nov 30 04:53:32 2017 From: jrd at netlab1.net (Joe Doupnik) Date: Thu, 30 Nov 2017 11:53:32 +0000 Subject: [sle-beta] Beta3 post install software installation In-Reply-To: <20171130115059.GA3869@suse.de> References: <46AC8C81C10B8C48820201DF2AE1D76D011F6F1387@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F13DD@daeexmbx1.eur.ad.sag> <46AC8C81C10B8C48820201DF2AE1D76D011F6F203C@daeexmbx1.eur.ad.sag> <40225827-e6a6-cce8-eb74-8f2a825b57d3@netlab1.net> <845d2b2d-3686-b5f5-5d29-7ab7168ab06a@netlab1.net> <20171129210106.GA4741@suse.de> <20171130115059.GA3869@suse.de> Message-ID: Thorsten and the group, ??? That is about right, both the need to install parallel SSL's for development and have the CA certs be installed. ??? Hopefully this will turn out to be a simple dependency matter to diagnose. ??? Thanks, ??? Joe D. On 30/11/2017 11:50, Thorsten Kukuk wrote: > Hi, > > On Thu, Nov 30, Joe Doupnik wrote: > >> Thorsten and the group, >> ??? Fair enough. What I am trying to do in this particular case is use >> Openssl v1.1 to support building an application, and see if existing apps >> could use it. The answer to the latter is typically no, of course, as they >> are built against v1.0.2, which is a situation similar to using the Security >> Channel of previous versions of SLES to supply a few key apps built with >> another version of SSL. Building my own code needs SSL v1.1 for checking >> matters, and that means both the library and the headers (-devel bundle). >> ? Where matters become sticky is adding the -devel material, where YaST >> decides that we must remove all of the earlier SSL material (thus the >> earlier library as well). I think that is a step too far in the dependency >> resolution problem, where there is conflict only about the -devel part. This >> seems to be readily curable by a script tweak or two. > Yes, it is currently not possible to install openssl v1.1 and v1.0 in > parallel, but this is what you need here. I hope our security team will > find a solution for this. > >> ??? Next there are the certificates. Right now this seems to be a muddle. I >> have two Beta 3 machines set up, one with the choice of SSL v1.1 and the >> second with the stock SSL v1.0.x. The first has experienced the discussed >> problems, and the second does work reasonably well. The certificate blockage >> does seem to be a dependency criteria which I have not decoded. >> ??? Here is a screen capture of one case: on the SSL v1.1 (first) machine. >> In YaST ask to install the ca-certificates RPM material, and the conflict >> resolution screen shown below appears: > That's a similar problem: YaST/zypper always tries to install the newest > version. You have to select the openssl-1.0 package manually. > But the question is: why is ca-certificates not installed? Should always > be installed. > > Thorsten >