-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1 from bossjones/feature-bump-gtk3-patch
Feature: gtk3 updates
- Loading branch information
Showing
7 changed files
with
258 additions
and
18 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,52 @@ | ||
| # -*- coding: utf-8 -*- | ||
|
|
||
| matrix: | ||
| fast_finish: true | ||
| include: | ||
| - python: '3.5' | ||
| env: | ||
| DOCKER_COMPOSE_VERSION: 1.8.0 | ||
| TEST_TARGET: default | ||
| DOCKER_DATA: "$HOME/docker_data" | ||
| DOCKER_VERSION: 17.03.1~ce-0~ubuntu-trusty | ||
| DOCKER_COMPOSE_VERSION: 1.8.0 | ||
| sudo: required | ||
| dist: trusty | ||
| language: python | ||
| group: edge | ||
|
|
||
| services: | ||
| - docker | ||
|
|
||
| before_install: | ||
| - sudo apt-get update | ||
| - travis_retry pip install coveralls | ||
| - sudo apt-cache search docker | ||
| # List available docker versions. | ||
| - apt-cache madison docker-ce | ||
| - sudo apt-get -y -o Dpkg::Options::="--force-confnew" install docker-ce=$DOCKER_VERSION | ||
| # Update Docker. See: https://graysonkoonce.com/managing-docker-and-docker-compose-versions-on-travis-ci/. | ||
| # - sudo apt-get -o Dpkg::Options::="--force-confnew" install -y --force-yes docker.io | ||
| # Add docker-compose at the version specified in ENV. | ||
| - sudo rm -f /usr/local/bin/docker-compose | ||
| - curl -L https://github.com/docker/compose/releases/download/${DOCKER_COMPOSE_VERSION}/docker-compose-`uname -s`-`uname -m` > docker-compose | ||
| - chmod +x docker-compose | ||
| - sudo mv docker-compose /usr/local/bin | ||
| - docker-compose --version | ||
|
|
||
| cache: | ||
| apt: true | ||
|
|
||
| install: | ||
| - travis_retry docker-compose pull | ||
| # set containers as privileged to bypass Travis environment limitations | ||
| - 'sed -i "/build: ./a \ \ privileged: true" docker-compose.yml' | ||
|
|
||
| script: | ||
| - travis_retry docker-compose -f docker-compose.yml -f ci_build.yml build | ||
|
|
||
| # source: https://github.com/inspirehep/inspire-next/blob/9700274c36074a3e43168bf48b8ba3e3bfa7bcdf/.travis.yml | ||
| after_script: | ||
| # Killing via SIGTERM in order to trigger atexit and dump coverage information in WSGI | ||
| - "docker-compose -f docker-compose.yml kill -s SIGTERM" | ||
|
|
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,15 @@ | ||
| # unable to set CAP_SETFCAP effective capability: Operation not permitted | ||
|
|
||
| ``` | ||
| [0m[91mI: Modulesets were edited locally but JHBuild is configured to get them from the network, perhaps you need to add use_local_modulesets = True to your /home/pi/.jhbuildrc. | ||
| [0m[91mlibtool: warning: relinking 'libgstbase-1.0.la' | ||
| [0m[91mlibtool: warning: relinking 'libgstcontroller-1.0.la' | ||
| [0m[91mlibtool: warning: relinking 'libgstnet-1.0.la' | ||
| [0m[91mlibtool: warning: relinking 'libgstcheck-1.0.la' | ||
| [0m[91munable to set CAP_SETFCAP effective capability: Operation not permitted | ||
| [0m[91mmake[5]: [install-data-hook] Error 1 (ignored) | ||
| [0m[91mlibtool: warning: relinking 'libgstcoreelements.la' | ||
| [0m[91mlibtool: warning: relinking 'libgstcoretracers.la' | ||
| ``` | ||
|
|
||
| https://unix.stackexchange.com/questions/106336/unable-to-set-capability-cap-setfcap-by-user |
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,41 @@ | ||
| # When to use exec? | ||
|
|
||
| `source: ` | ||
|
|
||
| `exec` replaces the current program in the current process, without forking a new process. It is not something you would use in every script you write, but it comes in handy on occasion. Here are some scenarios I have used it; | ||
|
|
||
| 1. We want the user to run a specific application program without access to the shell. We could change the sign-in program in /etc/passwd, but maybe we want environment setting to be used from start-up files. So, in (say) .profile, the last statement says something like: | ||
|
|
||
| `exec appln-program` | ||
|
|
||
| so now there is no shell to go back to. Even if appln-program crashes, the end-user cannot get to a shell, because it is not there - the exec replaced it. | ||
|
|
||
| 2. We want to use a different shell to the one in /etc/passwd. Stupid as it may seem, some sites do not allow users to alter their sign-in shell. One site I know had everyone start with csh, and everyone just put into their .login (csh start-up file) a call to ksh. While that worked, it left a stray csh process running, and the logout was two stage which could get confusing. So we changed it to exec ksh which just replaced the c-shell program with the korn shell, and made everything simpler (there are other issues with this, such as the fact that the ksh is not a login-shell). | ||
|
|
||
| 3. Just to save processes. If we call prog1 -> prog2 -> prog3 -> prog4 etc. and never go back, then make each call an exec. It saves resources (not much, admittedly, unless repeated) and makes shutdown simplier. | ||
| You have obviously seen exec used somewhere, perhaps if you showed the code that's bugging you we could justify its use. | ||
|
|
||
| Edit: I realised that my answer above is incomplete. There are two uses of exec in shells like ksh and bash - used for opening file descriptors. Here are some examples: | ||
|
|
||
| ``` | ||
| exec 3< thisfile # open "thisfile" for reading on file descriptor 3 | ||
| exec 4> thatfile # open "thatfile" for writing on file descriptor 4 | ||
| exec 8<> tother # open "tother" for reading and writing on fd 8 | ||
| exec 6>> other # open "other" for appending on file descriptor 6 | ||
| exec 5<&0 # copy read file descriptor 0 onto file descriptor 5 | ||
| exec 7>&4 # copy write file descriptor 4 onto 7 | ||
| exec 3<&- # close the read file descriptor 3 | ||
| exec 6>&- # close the write file descriptor 6 | ||
| ``` | ||
|
|
||
| Note that spacing is very important here. If you place a space between the fd number and the redirection symbol then exec reverts to the original meaning: | ||
|
|
||
|
|
||
| `exec 3 < thisfile # oops, overwrite the current program with command "3"` | ||
|
|
||
| There are several ways you can use these, on ksh use read -u or print -u, on bash, for example: | ||
|
|
||
| ``` | ||
| read <&3 | ||
| echo stuff >&4 | ||
| ``` |
Oops, something went wrong.