Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'jusa/pulseaudio-pa14.2'
- Loading branch information
Showing
330 changed files
with
45,458 additions
and
25,112 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,129 @@ | ||
# The build has two stages. The 'container' stage is used to build a Docker | ||
# container and push it to the project's container registry on fd.o GitLab. | ||
# This step is only run when the tag for the container changes, else it is | ||
# effectively a no-op. All of this infrastructure is inherited from the | ||
# wayland/ci-templates repository which is the recommended way to set up CI | ||
# infrastructure on fd.o GitLab. | ||
# | ||
# Once the container stage is done, we move on to the 'build' stage where we | ||
# run an autotools and meson build in parallel. Currently, tests are also run | ||
# as part of the build stage as there doesn't seem to be significant value to | ||
# splitting the stages at the moment. | ||
|
||
stages: | ||
- container | ||
- build | ||
|
||
variables: | ||
# Update this tag when you want to trigger a rebuild the container in which | ||
# CI runs, for example when adding new packages to FDO_DISTRIBUTION_PACKAGES. | ||
# The tag is an arbitrary string that identifies the exact container | ||
# contents. | ||
FDO_DISTRIBUTION_TAG: '2020-03-07-01' | ||
FDO_DISTRIBUTION_VERSION: '18.04' | ||
FDO_UPSTREAM_REPO: 'pulseaudio/pulseaudio' | ||
UBUNTU_IMAGE: "$CI_REGISTRY_IMAGE/ubuntu/$FDO_DISTRIBUTION_VERSION:$FDO_DISTRIBUTION_TAG" | ||
|
||
include: | ||
# We pull templates from master to avoid the overhead of periodically | ||
# scanning for changes upstream. This does means builds might occasionally | ||
# break due to upstream changing things, so if you see unexpected build | ||
# failures, this might be one cause. | ||
- project: 'wayland/ci-templates' | ||
ref: 'master' | ||
file: '/templates/ubuntu.yml' | ||
|
||
build-container: | ||
extends: .fdo.container-ifnot-exists@ubuntu | ||
stage: container | ||
variables: | ||
GIT_STRATEGY: none # no need to pull the whole tree for rebuilding the image | ||
|
||
# Remember to update FDO_DISTRIBUTION_TAG when modifying this package list! | ||
# Otherwise the changes won't have effect since an old container image will | ||
# be used. | ||
FDO_DISTRIBUTION_PACKAGES: >- | ||
autoconf | ||
automake | ||
autopoint | ||
bash-completion | ||
check | ||
curl | ||
dbus-x11 | ||
g++ | ||
gcc | ||
gettext | ||
git-core | ||
libasound2-dev | ||
libasyncns-dev | ||
libavahi-client-dev | ||
libbluetooth-dev | ||
libcap-dev | ||
libfftw3-dev | ||
libglib2.0-dev | ||
libgtk-3-dev | ||
libice-dev | ||
libjack-dev | ||
liblircclient-dev | ||
libltdl-dev | ||
liborc-0.4-dev | ||
libsbc-dev | ||
libsndfile1-dev | ||
libsoxr-dev | ||
libspeexdsp-dev | ||
libssl-dev | ||
libsystemd-dev | ||
libtdb-dev | ||
libtool | ||
libudev-dev | ||
libwebrtc-audio-processing-dev | ||
libwrap0-dev | ||
libx11-xcb-dev | ||
libxcb1-dev | ||
libxml-parser-perl | ||
libxml2-utils | ||
libxtst-dev | ||
make | ||
ninja-build | ||
pkg-config | ||
python3-setuptools | ||
systemd | ||
wget | ||
build-autotools: | ||
stage: build | ||
image: $UBUNTU_IMAGE | ||
script: | ||
- export MAKEFLAGS="-j$(nproc)" | ||
- NOCONFIGURE=1 ./bootstrap.sh | ||
- mkdir build | ||
- cd build | ||
- ../configure --localstatedir=/var | ||
- make | ||
- make check | ||
- make check-daemon | ||
- ulimit -c 0 # don't dump core files on tests that are supposed to assert | ||
- make distcheck | ||
artifacts: | ||
paths: | ||
- build/ | ||
|
||
build-meson: | ||
stage: build | ||
image: $UBUNTU_IMAGE | ||
script: | ||
# Install meson | ||
- wget -q https://github.com/mesonbuild/meson/releases/download/0.50.0/meson-0.50.0.tar.gz | ||
- tar -xf meson-0.50.0.tar.gz | ||
- cd meson-0.50.0 | ||
- python3 setup.py install | ||
- cd .. | ||
# Do the actual build | ||
- meson build | ||
- cd build | ||
- ninja | ||
- ninja test | ||
- ninja test-daemon | ||
artifacts: | ||
paths: | ||
- build/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
### Warning | ||
Missing data may cause bugs to languish. | ||
|
||
### Summary | ||
(Summarize the bug encountered concisely) | ||
|
||
### environment | ||
Check to see if you have pa-info installed by running `which pa-info` | ||
If yes please run it | ||
If no please download and run https://gitlab.freedesktop.org/pulseaudio/pulseaudio/blob/master/src/utils/pa-info | ||
Attach the output to this bug report as pa-info.txt | ||
|
||
### Steps to reproduce | ||
(How one can reproduce the issue - this is very important) | ||
|
||
|
||
### What is the current *bug* behavior? | ||
(What actually happens) | ||
|
||
### What is the expected *correct* behavior? | ||
(What you should see instead) |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
# Contributor Covenant Code of Conduct | ||
|
||
## Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as | ||
contributors and maintainers pledge to making participation in our project and | ||
our community a harassment-free experience for everyone, regardless of age, body | ||
size, disability, ethnicity, sex characteristics, gender identity and expression, | ||
level of experience, education, socio-economic status, nationality, personal | ||
appearance, race, religion, or sexual identity and orientation. | ||
|
||
## Our Standards | ||
|
||
Examples of behavior that contributes to creating a positive environment | ||
include: | ||
|
||
* Using welcoming and inclusive language | ||
* Being respectful of differing viewpoints and experiences | ||
* Gracefully accepting constructive criticism | ||
* Focusing on what is best for the community | ||
* Showing empathy towards other community members | ||
|
||
Examples of unacceptable behavior by participants include: | ||
|
||
* The use of sexualized language or imagery and unwelcome sexual attention or | ||
advances | ||
* Trolling, insulting/derogatory comments, and personal or political attacks | ||
* Public or private harassment | ||
* Publishing others' private information, such as a physical or electronic | ||
address, without explicit permission | ||
* Other conduct which could reasonably be considered inappropriate in a | ||
professional setting | ||
|
||
## Our Responsibilities | ||
|
||
Project maintainers are responsible for clarifying the standards of acceptable | ||
behavior and are expected to take appropriate and fair corrective action in | ||
response to any instances of unacceptable behavior. | ||
|
||
Project maintainers have the right and responsibility to remove, edit, or | ||
reject comments, commits, code, wiki edits, issues, and other contributions | ||
that are not aligned to this Code of Conduct, or to ban temporarily or | ||
permanently any contributor for other behaviors that they deem inappropriate, | ||
threatening, offensive, or harmful. | ||
|
||
## Scope | ||
|
||
This Code of Conduct applies both within project spaces and in public spaces | ||
when an individual is representing the project or its community. Examples of | ||
representing a project or community include using an official project e-mail | ||
address, posting via an official social media account, or acting as an appointed | ||
representative at an online or offline event. Representation of a project may be | ||
further defined and clarified by project maintainers. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported by contacting the project team at pulseaudio-maintainers@lists.freedesktop.org. All | ||
complaints will be reviewed and investigated and will result in a response that | ||
is deemed necessary and appropriate to the circumstances. The project team is | ||
obligated to maintain confidentiality with regard to the reporter of an incident. | ||
Further details of specific enforcement policies may be posted separately. | ||
|
||
Project maintainers who do not follow or enforce the Code of Conduct in good | ||
faith may face temporary or permanent repercussions as determined by other | ||
members of the project's leadership. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html | ||
|
||
[homepage]: https://www.contributor-covenant.org |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.