<metapackage xmlns:os="http://opensuse.org/Standards/One_Click_Install" xmlns="http://opensuse.org/Standards/One_Click_Install">
  <group>
    <repositories>
      <repository recommended="true">
        <name>Cloud:OpenStack:Queens</name>
        <summary> OpenStack Queens (Stable branch)</summary>
        <description>If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.
      
DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Queens:Staging!

</description>
        <url>https://download.opensuse.org/repositories/Cloud:/OpenStack:/Queens/openSUSE_Leap_42.3/</url>
      </repository>
      <repository recommended="true">
        <name>openSUSE:Leap:42.3:Update</name>
        <summary>Online updates for openSUSE Leap:42.3</summary>
        <description>This project is releasing the official updates for openSUSE Leap:42.3.</description>
        <url>https://download.opensuse.org/update/leap/42.3/oss/</url>
      </repository>
      <repository recommended="false">
        <name>openSUSE:Leap:42.3</name>
        <summary>openSUSE Leap 42.3</summary>
        <description></description>
        <url>https://download.opensuse.org/distribution/leap/42.3/repo/oss/</url>
      </repository>
    </repositories>
    <software>
      <item>
        <name>python-ptyprocess</name>
        <summary>Run a subprocess in a pseudo terminal</summary>
        <description>Launch a subprocess in a pseudo terminal (pty), and interact with both the
process and its pty.

Sometimes, piping stdin and stdout is not enough. There might be a password
prompt that doesn't read from stdin, output that changes when it's going to a
pipe rather than a terminal, or curses-style interfaces that rely on a terminal.
If you need to automate these things, running the process in a pseudo terminal
(pty) is the answer.</description>
      </item>
    </software>
  </group>
</metapackage>
