Just FYI: Current workaround is blacklisting the "libproxy1-config-kde4" package... ------------- <software> <remove-packages config:type="list"> <package>libproxy1-config-kde4</package> </remove-packages> </software> -------------
Best regards, Joschi Brauchle
On 10/22/2014 09:33 AM, Stefan Schubert wrote:
Thanks ! I will have a look on it.
Greetings Stefan Schubert Am 21.10.2014 um 18:44 schrieb Joschi Brauchle:
I figured it is NOT the same problem, as y2log of the second stage clearly shows a segmentation fault!
I filed: http://bugzilla.opensuse.org/show_bug.cgi?id=902086
Best regards, Joschi Brauchle
On 10/21/2014 05:40 PM, Joschi Brauchle wrote:
Thank you very much for the documentation.
Some more information on the broken installation: It looks like it is the *same* problem that existed for 13.1: the add-on section.
I did two installations, with this diff between xmls:
--- test.xml 2014-10-21 17:05:15.000000000 +0200 +++ test.xml.broken 2014-10-21 17:05:04.000000000 +0200 @@ -4,7 +4,14 @@ <add-on>
<product>OpenSUSE13.2 HTTP OBS:lnt-sysadmin:tools</product>
The installation *with* the add-on section specified is broken!
This looks pretty identical to https://bugzilla.novell.com/show_bug.cgi?id=846011
Shall I reopen or create new report?
As there are only 13 days to release, is there any chance to get this fixed before GM?
On 10/21/2014 11:28 AM, Stefan Schubert wrote:
is the latest documentation.
Am 21.10.2014 um 09:55 schrieb Joschi Brauchle:
I am currently trying to figure out what is going wrong with the 13.1 xml profile in 13.2. The installation is completely broken without any (gui) errors during the process.
But if I create a new profile for 13.2 from scratch, auto installation works fine. Thus, I'd like to revise my statement about Autoyast being broken, it is clearly not!
One question: Is there an up-to-date website that lists the changes from AY 13.1 to 13.2?
- http://doc.opensuse.org/projects/autoyast/ is about SLES11SP3
(which is strange as it is hosted by opensuse.org). 2) https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto...
the same 3) http://users.suse.com/~ug/ is outdated as of 12.2.
There seem to be a lot of changes to the installer (plus new modules like yast2-auth-client to configure sssd) but no documentation to be found (easily) for users...
Thanks, Joschi Brauchle
On 10/21/2014 09:26 AM, Stefan Schubert wrote:
Hi Joschi, please open a bug report and attach the logfiles and autoinst.xml Thanks !
Greetings Stefan Am 20.10.2014 um 23:58 schrieb Thomas Fehr: > Hi, > > On Mon, Oct 20, Joschi Brauchle wrote: > >> On 10/20/2014 02:21 PM, 686f6c6d wrote: >>> On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle >>> email@example.com wrote: >>>> Version 13.2 will be released in a couple of days and it looks >>>> like >>>> the >>>> autoinstalled is broken once again on the (to be) released >>>> medium. >>>> >>>> Hence, auto-installing will not work correctly for the complete >>>> lifetime of >>>> 13.2. This was the case for 12.x and 13.1 already, >>>> >>>> This is pretty frustrating... :-( >>> Meh. Damn. Does any bnc# exist for this? >> No, >> I am currently trying to sort out the problems and analyze. >> >> So far it looks like a 13.1 XML used for 13.2 results in a broken >> installation (i.e. all second stage steps are missing). >> I'll provide more information as soon as I know whats going wrong. >> >> Possibly, Thomas Fehr could comment on how the second stage >> works in >> 13.2 >> and what steps are needed to get it working, as it looks like it >> was >> dropped from the regular installer? > I am currently on a sabattical for a year that started 1.4.2014 . > Therefore my knowledge about developments that happened in the last > some months is quite limited. > > Autoyast maintainer is Stefan Schubert firstname.lastname@example.org. > I forwarded this thread to him. > > Tschuess, > Thomas Fehr