02-05-2020
Patching might not work - because the patch may assume versions of the link libraries that are different from what you linked in your original build.
Do you have a sandbox to test the patch? Try it there first. We have a couple of virtual boxes that we can play with for testing. We refresh them using the current production version. -- after we trash them.
9 More Discussions You Might Find Interesting
1. Programming
Is there anyone who still uses CMI to connect to the legacy system , my c applications do uses the binaries and libraries for using the CMI functionality but i do not have access to the original source code , and since this is a very old stuff , i just could not get any source to get to knwo the... (0 Replies)
Discussion started by: dino_leix
0 Replies
2. IP Networking
Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down.
I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies
3. Red Hat
Hello,
I am using Redhat Linux Enterprise 4 AS.
To upgrade NFS, I had to browse the internet and finally I got the latest rpm https://rhn.redhat.com/errata/RHBA-2005-727.html
That was a time-consuming procedure. On Solaris, I am used to go to sunfreeware.sun.com and download the latest... (3 Replies)
Discussion started by: melanie_pfefer
3 Replies
4. Programming
I need help locating the tables that hold the demograhic data in this system on an AIX box. Does anyone know the path? (0 Replies)
Discussion started by: Chelcye
0 Replies
5. Slackware
Hi!
Let me introduce a project for find and download Slackware packages and browse Slackware repositories.
The site provides following features:
* Large, daily updated database with RPM, DEB, TGZ, TXZ packages for well-known repositories of the Slackware, Fedora, CentOS, RHEL, Debian,... (2 Replies)
Discussion started by: lystor
2 Replies
6. Solaris
I have a Solaris 10 OS having kernal patch level 138888-03 on several servers but recenlty I upgraded it into 142900-12 on some T-Series servers & v890 server after install them my syslog is increasing at a rate of 1GB on average on all servers . I believe its a bug, can somebody help me in... (1 Reply)
Discussion started by: sb200
1 Replies
7. What is on Your Mind?
Watched it. Major disappointment. (10 Replies)
Discussion started by: ni2
10 Replies
8. Ubuntu
Hi folks,
Ubuntu 9.04
I have an old box not running for years. I just dig it out from the store room. On running;
$ sudo aptitude update
......
......
Err http://hk.archive.ubuntu.com jaunty/main Packages
404 Not Found
Err http://hk.archive.ubuntu.com jaunty/restricted Packages
... (1 Reply)
Discussion started by: satimis
1 Replies
9. Solaris
Hi Folks,
Just a quick question here, about Legacy Zones. Well more about how to determine if you are actually in one, on logging into a legacy zone - is there a quick way of checking that?
Regards
Gull04 (7 Replies)
Discussion started by: gull04
7 Replies
LEARN ABOUT DEBIAN
gbp-pq
GBP-PQ(1) git-buildpackage Manual GBP-PQ(1)
NAME
gbp-pq - Manage quilt patches on patch queue branches in git
SYNOPSIS
gbp-pq [ --verbose ] [ --color=[auto|on|off] ] [ --[no-]patch-numbers ] [ --topic=topic ] [ --time-machine=num ] drop | export | import |
rebase | switch
DESCRIPTION
gbp-pq helps one to manage quilt patches in Debian packages that are maintained with git-buildpackage. This is especially useful with pack-
ages using the 3.0 (quilt) source format. With gbp-pq you can maintain the quilt patches that should be applied to a package on a separate
branch called patch-queue branch. So if your Debian package lives on master the associated patch-queue branch will be called patch-
queue/master.
See <URL:https://honk.sigxcpu.org/piki/development/debian_packages_in_git/> for example workflows.
ACTIONS
import Create a patch queue branch from quilt patches in debian/patches/ that are listed in debian/patches/series.
export Export the patches on the patch-queue branch associated to the current branch into a quilt patch series in debian/patches/ and
update the series file.
rebase Switch to the patch-queue branch associated to the current branch and rebase it against the current branch.
drop Drop (delete) the patch queue associated to the current branch. So if you're on branch foo this would drop branch patch-queue/foo.
apply Add a single patch to the patch-queue similar to using git-am. Use --topic if you want the patch to appear in a separate subdir when
exporting the patch queue using export. This can be used to separate upstream pathes from debian specific patches.
switch Switch to the patch-queue branch if on the base branch and switch to base branch if on patch-queue branch.
OPTIONS
--verbose
-v verbose execution
--color=[auto|on|off]
Whether to use colored output.
--[no-]patch-numbers
Whether the patch files should start with a number or not.
--topic=topic
Topic to use when importing a single patch
--time-machine=NUM
When importing a patch queue fails, go back commit by commit on the current branch to check if the patch-queue applies there. Do
this at most NUM times. This can be useful if the patch-queue doesn't apply to the current branch HEAD anymore, e.g. after import-
ing a new upstream version.
TAGS
When exporting patches from a patch-queue branch gbp-pq will look at the patch header for special tags it recognizes. All tags need to
start at the first column and require at least one whitespace after the colon.
Gbp-Pq-Topic: topic
Moves the patch into a subdir called topic when running
gbp-pq
export
. This allows for some structure below debian/patches.
SEE ALSO
git-buildpackage(1), dpkg-source(1), quilt(1), gbp.conf(5)
AUTHOR
Guido Guenther <agx@sigxcpu.org>
01 June 2012 GBP-PQ(1)