Dirk Mueller's avatar

You are behind a proxy. You can modify other data related to your profile by this link.

Dirk Mueller's avatar

Dirk Mueller

dirkmueller

Member of the groups
Involved Projects and Packages
Maintainer

A unix communication package providing the xmodem, ymodem and zmodem file transfer protocols.

Maintainer

Sed takes text input, performs one or more operations on it, and outputs the modified text. Sed is typically used for extracting parts of a file using pattern matching or for substituting multiple occurrences of a string within a file.

Maintainer

The sg3_utils package contains utilities that send SCSI commands to
devices. As well as devices on transports traditionally associated with
SCSI (e.g. Fibre Channel (FCP), Serial Attached SCSI (SAS) and the SCSI
Parallel Interface(SPI)) many other devices use SCSI command sets.
ATAPI cd/dvd drives and SATA disks that connect via a translation layer
or a bridge device are examples of devices that use SCSI command sets.

Maintainer

SMARTmontools controls and monitors storage devices using the Self-Monitoring, Analysis, and Reporting Technology System (S.M.A.R.T.) built into ATA, SATA and SCSI Hard Drives. This is used to check the hard drive reliability and to predict drive failures. The suite contains two utilities. The first, smartctl, is a command line utility designed to perform simple S.M.A.R.T. tasks. The second, smartd, is a daemon that periodically monitors the smart status and reports errors to syslog. The package is compatible with the ATA/ATAPI-3 to -7 specification. The package is intended to incorporate as much "vendor specific" and "reserved" information as possible about disk drives. The commands man smartctl and man smartd will provide more information.

Maintainer

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer
Maintainer

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer Bugowner

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer

NOTE: Automatically created during Factory devel project migration by admin.

Maintainer

This project is created to handle non-release versions of u-boot for testing

Maintainer

Base project for everything around working with clouds. This project contains only software that is shared among all sub-projects.

Maintainer

This is a collection of packages needed to maintain and run additional software components of the Cloud related CI jobs.
It is a central place to collect these dependencies only by linking to packages maintained elsewhere (preferably Factory, devel-projects).

Maintainer

The images and packages are built in sub-projects named after the distributions for which they are built. This project should in general be empty.

Maintainer

A massively scalable cloud operating system. This project is only a container and includes the following sub-projects:

Cloud:OpenStack:Factory - The current stable version for openSUSE (openSUSE:Factory devel project)
Cloud:OpenStack:Master - Latest packaged upstream version and bleeding-edge development
Cloud:OpenStack:Train - The OpenStack Train release
Cloud:OpenStack:Stein - The OpenStack Stein release
Cloud:OpenStack:Rocky - The OpenStack Rocky release
Cloud:OpenStack:Queens - The OpenStack Queens release - EOL
Cloud:OpenStack:Pike - The OpenStack Pike release
Cloud:OpenStack:Ocata - The OpenStack Ocata release - EOL
Cloud:OpenStack:Newton - The OpenStack Newton release
Cloud:OpenStack:Mitaka - The OpenStack Mitaka release EOL
Cloud:OpenStack:Liberty - The OpenStack Liberty release EOL
Cloud:OpenStack:Kilo - The OpenStack Kilo release - EOL
Cloud:OpenStack:Juno - The OpenStack Juno release - EOL
Cloud:OpenStack:Icehouse - The OpenStack Icehouse release - EOL
Cloud:OpenStack:Havana - The OpenStack Havana release - EOL
Cloud:OpenStack:Grizzly - The OpenStack Grizzly release - EOL
Cloud:OpenStack:Folsom - The OpenStack Folsom release - EOL
Cloud:OpenStack:Essex - The OpenStack Essex release - EOL

There is also Cloud:OpenStack:Upstream:Master (and other subprojects under Cloud:OpenStack:Upstream). These packages are automatically generated from the RPM-packaging project (see https://wiki.openstack.org/wiki/Rpm-packaging)
Some further links that may be of interest:

OpenStack project: http://www.openstack.org
OpenStack releases: https://releases.openstack.org/
SUSE Cloud product: http://suse.com/cloud
http://en.opensuse.org/openSUSE:OpenStack_and_Crowbar_development_process

A massively scalable cloud operating system.

Contains always the latest stable OpenStack release based on the SUSE Cloud product and is used as a devel project for openSUSE:Factory.

##################################################################
MOST OF THE PACKAGES ARE MAINTAINED AT https://opendev.org/openstack/rpm-packaging/ .
Please use the gerrit workflow to submit patches
##################################################################

OpenStack project: http://www.openstack.org
SUSE Cloud product: http://suse.com/cloud

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:Havana:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Havana). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branche
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Havana)!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Icehouse). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branche
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Icehouse)!

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:Juno:Staging!

openSUSE Build Service is sponsored by