Sponsored Content
Top Forums Web Development LAMP - version updates and the impact! Post 302522041 by pludi on Friday 13th of May 2011 06:38:35 AM
Old 05-13-2011
Usually nothing bad should happen, since all long-term distributions (CentOS, Ubuntu LTS, Debian Stable, ...) do not automatically upgrade a package to a different version, but only apply bug- and security fixes. So PHP (for example) will get bugfixes while still available, but it won't be upgraded to 5.2.x or 5.3.x.
 

8 More Discussions You Might Find Interesting

1. AIX

unix updates- Where can I find unix updates online for IBM servers?

I have a Unix based server running Sagitta and the server is giving me an error of 4b10004 and my research tells me this is an EPROM issue, which means the processor needs to be flashed or repaired. Once up and running where can I go to get updates for Unix? (1 Reply)
Discussion started by: crainer
1 Replies

2. UNIX for Dummies Questions & Answers

LAMP configuration

Hi there, I've got a debian 3.1r4 half working (no x yet :P) I need some pointers for installing a Apache - MySQL - PHP configuration on my box, and set them up to work together. I know to use vim a bit :) I would like something that is similar to tanguay.at, or even simpler, since I'm a real... (1 Reply)
Discussion started by: izua
1 Replies

3. Web Development

lamp performance

Hi all, My company run a CMS (typo3) on LAMP on RH linux. Basically all users have same typo3 page as home page and thousands of users starts their browser every morning causing server very slow or even to hang (swap full because of too many apache processes).. 99% of the traffic is this... (13 Replies)
Discussion started by: manifesto
13 Replies

4. Solaris

Need LAMP tutorial!

Hello Everybody, Does anybody know or recommend me a tutorial for LAMP server on Solaris 10 x86? (3 Replies)
Discussion started by: ahmedamer12
3 Replies

5. Web Development

Building LAMP server from scratch (build a server with compiled LAMP from CentOS mini)

Hello everyone, I would like to setup a lamp server from a minimal distro and to compile PHP, MySQL and Apache myself. I have chosen CentOS minimal for the OS and I am trying to build the stack by hand... But well, it appears I need some help! First: I am looking for good and recent... (3 Replies)
Discussion started by: freddie50
3 Replies

6. Programming

Lamp tutorial

Hello All, I need a good lamp(linux, apache, mysql, php) tutorial for web development. I searched in net but not finding suitable one. suggest me something. (3 Replies)
Discussion started by: amisubha
3 Replies

7. HP-UX

LAMP Installation On HP-UX

Dear Folks, How to Install LAMP on HP-UX system. Please Guide. Regards, KRISHNA (2 Replies)
Discussion started by: krishna.lu
2 Replies

8. UNIX for Advanced & Expert Users

LAMP Sever

How do I install a LAMP server on a new installation of Debian 9 using the lalest versions of AMP? Here is what I have. Corrections please. MYSQL apt-get install mysql-server mysql-client You can verify the MySQL server status using command: systemctl status mysql ------- PHP7... (0 Replies)
Discussion started by: Meow613
0 Replies
REQUESTSYNC(1)						      General Commands Manual						    REQUESTSYNC(1)

NAME
requestsync - helper to file sync requests for Ubuntu SYNOPSIS
requestsync [-d distro] [-nse] [-k keyid] <source package> [target release] [base version] requestsync --lp [-nse] <source package> <target release> [base version] requestsync -h DESCRIPTION
requestsync looks at the versions of <source package> in Debian and Ubuntu and prompts for an explanation of why the Ubuntu changes (if there are any) should be dropped. The changelog entry is then downloaded from packages.debian.org, and the sync request bug is filed in launchpad. Alternatively, the sync request can be filed by GPG-signed email (option --email). requestsync checks if you have the permissions to request the sync from the archive administrators directly by checking if you have upload permissions for that package through package set permissions or component permissions. If you don't have upload permissions, the script will subscribe the necessary team with approval rights to the bug report for you. This check is only performed if requestsync is allowed to use the LP API (not email submission). In the other case requestsync relies on that you answer the question about upload permissions honestly to determine if a team with approval rights is to be subscribed to the bug. If you have permission to upload the package directly, then you may prefer to use syncpackage instead to copy the package using the Launch- pad API. At some future point, requestsync will be changed to do this automatically. requestsync uses launchpadlib authentication to file its requests. OPTIONS
Listed below are the command line options for requestsync: -h Display a help message and exit. -d Specifies which Debian distribution a package should be synced from. Default is testing in LTS cycles, otherwise unstable. -n Specifies that the package is a new package, and requestsync should not attempt to look it up in Ubuntu since it will not exist. -k <keyid> Specifies your GPG key. This is only used if the sync request is mailed to Launchpad. --email Use GPG-signed email to file the bug, rather than launchpadlib. -s Specifies that you require sponsorship. You need this option if you don't have upload permissions for that package. This disables the upload permissions check described above. -C Allow changelog to be manually filled in when missing. requestsync gets Debian changelogs from packages.debian.org, which isn't in sync with the Debian archive. To request a sync before the changelog is available, pass this option, and provide the changelog entries yourself. -e Use this flag after FeatureFreeze for non-bug fix syncs. requestsync will subscribe ubuntu-release team instead of sponsorship team. -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. <source package> This is the source package that you would like to be synced from Debian. <target release> This is the release that you would like the source package to be synced into. This should always be the latest development release of Ubuntu. [base version] In some cases, the base version (where the Ubuntu package started differing from the Debian package) cannot be automatically deter- mined. Specify this option in this case. ENVIRONMENT
requestsync uses the following variables which should be set in your shell's configuration by adding export VARIABLE= lines, where VARIABLE is one of the following: UBUMAIL, DEBEMAIL Specifies which email should be used when sending to Launchpad. 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
REQUESTSYNC_SMTP_SERVER Set which SMTP server to use when sending mail. If unspecified this defaults to launchpad's SMTP servers (the eventual destina- tion). REQUESTSYNC_SMTP_PORT Sets which port of the SMTP server to use. Default is 25. REQUESTSYNC_SMTP_USER and REQUESTSYNC_SMTP_PASS Sets the username and password to use when authenticating to the SMTP server. REQUESTSYNC_USE_LPAPI Setting this to no is equivalent to running with --email. REQUESTSYNC_LPINSTANCE, UBUNTUTOOLS_LPINSTANCE The default value for --lpinstance. REQUESTSYNC_KEYID, UBUNTUTOOLS_KEYID The default value for -k. SEE ALSO
rmadison(1), syncpackage(1), ubuntu-dev-tools(5) AUTHOR
requestsync and this manual page were written by the Ubuntu MOTU Team. Both are released under the GNU General Public License, version 2. ubuntu-dev-tools 19 January 2008 REQUESTSYNC(1)
All times are GMT -4. The time now is 05:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy