Tor is a connection-based low-latency anonymous communication system.

This package provides the "tor" program, which serves as both a client and
a relay node. Scripts will automatically create a "%{toruser}" user and
a "%{torgroup}" group, and set tor up to run as a daemon when the system
is rebooted.

Applications connect to the local Tor proxy using the SOCKS
protocol. The local proxy chooses a path through a set of relays, in
which each relay knows its predecessor and successor, but no
others. Traffic flowing down the circuit is unwrapped by a symmetric
key at each relay, which reveals the downstream relay.

Warnings: Tor does no protocol cleaning. That means there is a danger
that application protocols and associated programs can be induced to
reveal information about the initiator. Tor depends on Privoxy and
similar protocol cleaners to solve this problem. This is alpha code,
and is even more likely than released code to have anonymity-spoiling
bugs. The present network is very small -- this further reduces the
strength of the anonymity provided. Tor is not presently suitable
for high-stakes anonymity.

Authors:
--------
- R. Dingledine

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

PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. It combines signaling protocol (SIP) with rich multimedia framework and NAT traversal functionality into high level API that is portable and suitable for almost any type of systems ranging from desktops, embedded systems, to mobile handsets.

These are the developer versions of the tools for the Open Build Service project. They are mainly used by the openSUSE instance.

Please use OBS:Server:2.10 for production environments unless told otherwise.

This is a pluggable command-line tool. It includes some built-in features:

* Create file layouts for packages.
* Serving up web applications, with configuration based on paste.deploy

This is a pluggable command-line tool. It includes some built-in features:

* Create file layouts for packages.
* Serving up web applications, with configuration based on paste.deploy

https://en.opensuse.org/openSUSE:Slowroll
a derivative codestream of openSUSE:Factory/ALP:Source:Rolling that uses automated rules to limit the rate of change to the codebase

Experiment Owner: bmwiedemann

https://www.zq1.de/~bernhard/linux/opensuse/slowroll/slowroll-vs-tumbleweed-updates.svg

https://en.opensuse.org/openSUSE:Slowroll = a derivative codestream of openSUSE:Factory that uses automated rules to limit the rate of change to the codebase

Release manager: bmwiedemann

https://www.zq1.de/~bernhard/linux/opensuse/slowroll/slowroll-vs-tumbleweed-updates.svg

Before a version bump, I collect i586 and bootstrap binaries here. These are missing in released Tumbleweed snapshots, but are needed for building packages. Also binaries required for DVD builds, because product-builder cannot use those from download-on-demand (dod)

Before a version bump, I collect i586 and bootstrap binaries here. These are missing in released Tumbleweed snapshots, but are needed for building packages. Also binaries required for DVD builds, because product-builder cannot use those from download-on-demand (dod)

This provides an easy-to-use redirect for both sources and binaries in openSUSE:Slowroll:Base:1/2, switching every cycle (every month)

for building packages that are later released into openSUSE:Slowroll as updates

https://en.opensuse.org/openSUSE:Slowroll area for building and openQA testing

https://en.opensuse.org/openSUSE:Slowroll area for building and openQA testing

This is hard with product-builder, because it does not work with dod.

Packages that are specific to Slowroll and not auto-updated with the normal daily scripts.

slowrollbot will send individual packages here
and after that trigger a release of the whole project
so that only one repo-publish event happens on the main openSUSE:Slowroll update repo.

slowrollbot will send individual packages here
and after that trigger a release of the whole project
so that only one repo-publish event happens on the main openSUSE:Slowroll update repo.

slowrollbot will send individual packages here
and after that trigger a release of the whole project
so that only one repo-publish event happens on the main openSUSE:Slowroll update repo.

some packages are missing in Factory.
It is preferred to submit them into Factory, to give them proper review (legal and otherwise).