Sponsored Content
Full Discussion: Can not update my system
Operating Systems Linux Ubuntu Can not update my system Post 302807419 by DGPickett on Tuesday 14th of May 2013 04:14:09 PM
Old 05-14-2013
Maybe you are too far out of date, and the URLs are ng, so install the latest.
 

8 More Discussions You Might Find Interesting

1. AIX

System crash when update TL

Hello everyone I have a partition with the TL 5300-06-01-0000 and try to update to this TL 5300-09-03-0918 but suddenly the update dont work more. I get in to the HMC and I see this code error 888 102 700 0C5 I try to restart my partition but doesnt work. Theres someone who has this... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies

2. AIX

System P firmware update

I am interested whether should AIX Admin make upgrade of firmware on power systems or IBM support should do it thanks in advance :-) (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies

3. Solaris

Install update 6 on solaris with update 3

I want to update my solaris 10 server which is currently on update 3 stage. A new application require it to be on update 6. What is the best way to make it update 6. should i just install the patch or should i go for the liveupgrade?? thanks for you help in advance (3 Replies)
Discussion started by: uxravi
3 Replies

4. Programming

MYSQL - trigger update on record insert or update

Right I have a MYSQL database with table1 with 3 columns, colA, colB and colC. I want to combine the data in the 3 columns into a 4th column names col_comb. Here's the SQL command that works: UPDATE table1 SET `col_comb` = CONCAT( `colA` , ' - ', `colB` , ', ', `colC` ); So now I want this... (5 Replies)
Discussion started by: barrydocks
5 Replies

5. Red Hat

RedHat 5 update 9 BASH update issue

Hi i want to update the BASH because of the "shell shock" vulnerability. my RedHat 5 is clean install with the default mirror site. when im running the command: yum update bash im getting a message saying there is no update. you can see in the attach picture... what am i doing wrong? is... (4 Replies)
Discussion started by: guy3145
4 Replies

6. What is on Your Mind?

UNIX.com email system update

There seems to have been a small recurring problem with the forums not always sending email; so I have changed the system and tested it and it's all working OK now. Please post back if you have any trouble sending or receiving email from the forums (with details of course!) Thanks, Neo (1 Reply)
Discussion started by: Neo
1 Replies

7. AIX

Cloning a system via mksysb backup from one system and restore to new system

Hello All, I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance. Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies

8. Solaris

How to update Solaris 10 Update 3 to Update 11?

Hi friends, We have a Solaris machine running 10 update 3 -bash-3.2# cat /etc/release Solaris 10 11/06 s10s_u3wos_10 SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. ... (6 Replies)
Discussion started by: prvnrk
6 Replies
BACKPORTPACKAGE(1)					      General Commands Manual						BACKPORTPACKAGE(1)

NAME
backportpackage - helper to test package backports SYNOPSIS
backportpackage [additional options] --upload <upload target> <source package name or .dsc URL/file> backportpackage -h DESCRIPTION
backportpackage fetches a package from one distribution release or from a specified .dsc path or URL and creates a no-change backport of that package to one or more Ubuntu releases release, optionally doing a test build of the package and/or uploading the resulting backport for testing. Unless a working directory is specified, the backported package is fetched and built in a temporary directory in /tmp, which is removed once the script finishes running. backportpackage is only recommended for testing backports in a PPA, not uploading backports to the Ubuntu archive. OPTIONS
-d DEST, --destination=DEST Backport the package to the specified Ubuntu release. If this option is unspecified, then backportpackage defaults to the release on which it is currently running. -s SOURCE, --source=SOURCE Backport the package from the specified release, which can be any release of your distribution or any of your distribution's parent distributions. If neither this option nor --version are specified, then backportpackage defaults to the current development release for your distribution. -S SUFFIX, --suffix=SUFFIX Add the specified suffix to the version number when backporting. backportpackage will always append ~ubuntuDESTINATION.1 to the original version number, and if SUFFIX is specified, it is appended to that, to get version numbers of the form ORIGINAL_VER- SION~ubuntuDESTINATION.1SUFFIX. If the backported package is being uploaded to a PPA, then SUFFIX defaults to ~ppa1, otherwise the default is blank. -b, --build Build the package with the specified builder before uploading. Note for cowbuilder(8) and pbuilder(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 specified 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). -U, --update Update the build environment before attempting to build. -u UPLOAD, --upload=UPLOAD Upload to UPLOAD with dput(1) (after confirmation). -k KEYID, --key=KEYID Specify the key ID to be used for signing. --dont-sign Do not sign the upload. -y, --yes Do not prompt before uploading to a PPA. For everyone's safety, this option is ignored if UPLOAD is ubuntu. -v VERSION, --version=VERSION If the --source option is specified, then backportpackage verifies that the current version of source package in SOURCE is the same as VERSION. Otherwise, backportpackage finds version VERSION of source package in your distribution's publishing history, regardless of the release in which it was published (or if that version is still current). This option is ignored if a .dsc URL or path is passed in instead of a source package name. -w WORKDIR, --workdir=WORKDIR If WORKDIR is specified, then all files are downloaded, unpacked, built into, and otherwise manipulated in WORKDIR. Otherwise, a temporary directory is created, which is deleted before backportpackage exits. -r, --release-pocket Target the upload at the release pocket, rather than the -backports pocket. This is required for Launchpad PPAs, which are pocket- less (and the default, when the upload target is a PPA). -m MIRROR, --mirror=MIRROR Use the specified mirror. Should be in the form http://archive.ubuntu.com/ubuntu. If the package isn't found on this mirror, back- portpackage will use Launchpad. -c BUG, --close=BUG Include a Launchpad closer for the specified bug in the auto-generated changelog. In the future, this may actually close the bug, but currently does not. -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. ENVIRONMENT
DEBFULLNAME, DEBEMAIL, UBUMAIL Used to determine the uploader (if not supplied as options). See ubuntu-dev-tools(5) for details. 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. BACKPORTPACKAGE_BUILDER, UBUNTUTOOLS_BUILDER The default value for --builder. BACKPORTPACKAGE_UPDATE_BUILDER, UBUNTUTOOLS_UPDATE_BUILDER The default value for --update. BACKPORTPACKAGE_UPLOAD The default value for --upload. BACKPORTPACKAGE_WORKDIR, UBUNTUTOOLS_WORKDIR The default value for --workdir. BACKPORTPACKAGE_UBUNTU_MIRROR, UBUNTUTOOLS_UBUNTU_MIRROR The default value for --mirror if the specified SOURCE release is an Ubuntu release. BACKPORTPACKAGE_DEBIAN_MIRROR, UBUNTUTOOLS_DEBIAN_MIRROR The default value for --mirror if the specified SOURCE release is a Debian release. BACKPORTPACKAGE_LPINSTANCE, UBUNTUTOOLS_LPINSTANCE The default value for --lpinstance. EXAMPLES
Test-build in your PPA a backport of znc from the current development release to your workstation's release, deleting the build products afterwards: backportpackage -u ppa:user/ppa znc Backport squashfs-tools from Maverick to both Karmic and Lucid and test-build both locally, leaving all build products in the current work- ing directory: backportpackage -b -s maverick -d karmic -d lucid -w . squashfs-tools Fetch a package from a PPA, backport it to Hardy, then upload it back to the same PPA: backportpackage -d hardy -u ppa:user/ppa https://launchpad.net/some/file.dsc SEE ALSO
ubuntu-dev-tools(5) AUTHOR
backportpackage and this manpage were written by Evan Broder <evan@ebroder.net> Both are released under GNU General Public License, version 2. ubuntu-dev-tools December 2010 BACKPORTPACKAGE(1)
All times are GMT -4. The time now is 09:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy