Re: State of Autoyast for OpenSUSE 13.1

On Thu, Jan 30, 2014 at 10:40 AM, Joschi Brauchle
<[email protected]> wrote:
> Is this a known problem? Or are there known problems for 13.1?

This is a known bug (BNC# below), it was discussed on this ML a few
weeks back. You need to remove your <add-on> section completely.

It is "fixed" already, but fixed in the case of AutoYAST sadly always
means "only fixed in the next release", even for crippling bugs like
this, that affects every single user. For that particular problem I'm
using the following <post-script>:

---------- 8< ----------
      <!-- workaround for BNC#846011 (fixed for 13.2 since ~2014-01-26) -->
      <script>
        <network_needed config:type="boolean">true</network_needed>
        <filename>post-manual-repos</filename>
        <interpreter>shell</interpreter>
        <source><![CDATA[#!/bin/bash
# doesn't work in pre: read-only fs.

# install repo is added by install= cmdline param.

echo "[suse_update]
name=SUSE updates (13.1)
enabled=1
autorefresh=1
baseurl=http://repohost/suse/update/13.1/
type=rpm-md
gpgcheck=1
gpgkey=http://repohost/suse/update/13.1/repodata/repomd.xml.key" >>
/etc/zypp/repos.d/update.repo

echo "[something_stable]
name=something (13.1)
enabled=1
autorefresh=1
baseurl=http://repohost/acmecorp/something:/stable/openSUSE_13.1/
type=rpm-md
gpgcheck=1
gpgkey=http://repohost/acmecorp/something:/stable/openSUSE_13.1/repodata/repomd.xml.key"
>> /etc/zypp/repos.d/something.repo
]]></source>
      </script>
---------- >8 ----------


I don't remember any new problems in 13.1 from the top of my head
right now (maybe the problem with empty resolv.conf I had in 12.x now
happens in an earlier stage, not sure). Will post if I find something,
our profiles are quite huge nowaways.


-- 
Kind regards
    Christopher 'm4z' Holm / 686f6c6d

"We must respect the other fellow's religion, but only in the sense
and to the extent that we respect his theory that his wife is
beautiful and his children smart." --H. L. Mencken
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]