7 More Discussions You Might Find Interesting
1. Programming
With a little bit of work, was able to build a nice "Wuhan Coronavirus Status" app using MQTT and the IoT-OnOff app. More on this technique here:
ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages
The result turned out nice, I think. I like the look and... (10 Replies)
Discussion started by: Neo
10 Replies
2. UNIX for Beginners Questions & Answers
Hello Forum,
I'm issuing a one line bash command to look for the version of an installed application and saving the result to a variable like so:
APP=application --version
But if the application is not installed I want to return to my variable that the Application is not installed. So I'm... (2 Replies)
Discussion started by: greavette
2 Replies
3. Shell Programming and Scripting
Hi,
I am trying to restrict an ssh-user to execute unwanted commands using ssh from a remote host a. So for that I am using the forced command in the authorized_keys file that will allow the ssh-user to only execute a particular command.
If I did not set this, I am able to login via ssh and... (2 Replies)
Discussion started by: Anil George
2 Replies
4. Shell Programming and Scripting
df generates the following output on one of our systems:
df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vx/dsk/rootvol 4131866 3593316 497232 88% /
swap 19963152 144 19963008 1% /var/run
swap 19985184 ... (6 Replies)
Discussion started by: shew01
6 Replies
5. Programming
Hi-
I need the cpp call that will tell me the full path to the app I'm running in. For example, I'm running in a loaded library for either mozilla or firefox, but would like to know the full path to the executable
/usr/bin/firefox
/usr/bin/mozilla
/usr/local/firefox1_5
etc...
(For... (4 Replies)
Discussion started by: erwinfletch
4 Replies
6. Linux
I would like to know more about SIP technology (Session Initiation Protocol).
I have some trouble with SIP eXpress router and VoIP trasfer from server to client .
-The server is working and the client uses Xtensoftphone but the client can not to register in server .
-I need some more... (0 Replies)
Discussion started by: hydra
0 Replies
7. UNIX for Advanced & Expert Users
Hi, how could I find whether an application is installed by root or non-root
I am assuming it would be logged in a file, if it is where would it be?
Thanks in advance. (2 Replies)
Discussion started by: dtamminx
2 Replies
sponsor-patch(1) General Commands Manual sponsor-patch(1)
NAME
sponsor-patch - Prepare, test-build, and sponsor an upload.
SYNOPSIS
sponsor-patch [options] bug
sponsor-patch -h
DESCRIPTION
sponsor-patch downloads the patch or Bazaar branch linked to an Ubuntu bug, applies it, generates a review diff, (optionally) test builds
it, runs lintian(1) and, after review and confirmation, can upload it.
sponsor-patch can be used for sponsoring patches, syncs and merges from Debian, SRUs, and creating debdiffs from patches. If bug has mul-
tiple patches or branches linked, it will prompt the user to select one. The same applies to bug tasks. If the attached patch is not a
debdiff, edit-patch(1) is used to apply it.
Some obvious checks are performed, in particular:
1. update-maintainer(1) is run on the source package to ensure that the Maintainer field meets the Ubuntu policy.
2. The version number must be greater than the current version in the archive. The changes file is also correctly generated to list all
changes since the current version in the archive.
3. The changelog must automatically close the sponsorship bug.
4. The changelog target must be valid.
5. The changelog timestamp is touched.
Should any checks (or the build) fail, the user has an option to edit the patched source and try building it again.
Unless a working directory is specified, the sources and patches will be downloaded into a temporary directory in /tmp, which is removed
once the script finishes running. The output of the build tool will be placed in workdir/buildresult/.
One of --upload, --workdir, or --sponsor must be specified.
OPTIONS
-b, --build
Build the package with the specified builder. Note for pbuilder(8) and cowbuilder(8) users: This assumes the common configuration,
where the ARCH and DIST environment is read by pbuilderrc(5) to select the correct base image.
-B BUILDER, --builder=BUILDER
Use the specify builder to build the package. Supported are cowbuilder(8), cowbuilder-dist(1), pbuilder(8), pbuilder-dist(1), and
sbuild(1). The default is pbuilder(8).
-e, --edit
Launch a sub-shell to allow editing of the patched source before building.
-h, --help
Display a help message and exit.
-k KEY, --key=KEY
Specify a key ID for signing the upload.
-l INSTANCE, --lpinstance=INSTANCE
Use the specified instance of Launchpad (e.g. "staging"), instead of the default of "production".
--no-conf
Do not read any configuration files, or configuration from environment variables.
-s, --sponsor
Shortcut for sponsored uploads. Equivalent to -b -u ubuntu.
-u DEST, --upload=DEST
Upload to DEST with dput(1) (after confirmation).
-U, --update
Update the build environment before attempting to build.
-v, --verbose
Print more information.
-w DIR, --workdir=DIR
Use the specified working directory, creating it if necessary. If WORKDIR is not specified, a temporary directory is created, which
is deleted before sponsor-patch exits.
ENVIRONMENT
All of the CONFIGURATION VARIABLES below are also supported as environment variables. Variables in the environment take precedence to
those in configuration files.
CONFIGURATION VARIABLES
The following variables can be set in the environment or in ubuntu-dev-tools(5) configuration files. In each case, the script-specific
variable takes precedence over the package-wide variable.
SPONSOR_PATCH_BUILDER, UBUNTUTOOLS_BUILDER
The default value for --builder.
SPONSOR_PATCH_LPINSTANCE, UBUNTUTOOLS_LPINSTANCE
The default value for --lpinstance.
SPONSOR_PATCH_UPDATE_BUILDER, UBUNTUTOOLS_UPDATE_BUILDER
The default value for --update.
SPONSOR_PATCH_WORKDIR, UBUNTUTOOLS_WORKDIR
The default value for --workdir.
SPONSOR_PATCH_KEYID, UBUNTUTOOLS_KEYID
The default value for --key.
EXAMPLES
Test-building and sponsoring an upload of bug 1234:
sponsor-patch -s 1234
Performing a test build of bug 1234 in your PPA:
sponsor-patch -u ppa:user/ppa 1234
SEE ALSO
bzr(1), debchange(1), debdiff(1), dput(1), edit-patch(1), lintian(1), cowbuilder(8), cowbuilder-dist(1), pbuilder(8), pbuilder-dist(1),
sbuild(1), ubuntu-dev-tools(5), update-maintainer(1)
AUTHORS
sponsor-patch was written by Benjamin Drung <bdrung@ubuntu.com>, and this manual page was written by Stefano Rivera <stefanor@ubuntu.com>.
Both are released under the terms of the ISC License.
ubuntu-dev-tools September 21 2010 sponsor-patch(1)