Sponsored Content
Top Forums UNIX for Advanced & Expert Users Upgrading legacy packages with patch Post 303043765 by jim mcnamara on Wednesday 5th of February 2020 10:57:11 PM
Old 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

CMI Legacy

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

Patch-o-matic (patch for iptable) for linux2.4.08 & iptable1.2.7a

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

upgrading packages

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

VERSYS Legacy System

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

Find Slackware Packages - packages.acl.org.ua

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

Facing problem after upgrading the kernal patch level to 142900-12

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?

Tron Legacy

Watched it. Major disappointment. (10 Replies)
Discussion started by: ni2
10 Replies

8. Ubuntu

Encountering problem on upgrading the packages

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

Determine if you are in a Legacy Zone?

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
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)
All times are GMT -4. The time now is 06:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy