From 12ecc03eaf30160d396c0e0ff0f164dbcbb023c6 Mon Sep 17 00:00:00 2001 From: Matej Kollar Date: Thu, 8 Jan 2015 21:09:53 +0100 Subject: [PATCH] Getting rid of Tabs and trailing spaces in LICENSE, COPYING, and README files --- LICENSE | 14 +- backend/LICENSE | 14 +- backend/test/reactivation/README | 2 +- branding/LICENSE | 14 +- .../apt-transport-spacewalk/LICENSE | 14 +- .../python-ethtool/COPYING | 14 +- .../rhn-client-tools/doc/LICENSE | 14 +- .../rhn-client-tools/src/actions/README | 90 ++++----- .../packages-already-in-debian/rhnlib/README | 6 +- .../packages-already-in-debian/rhnsd/LICENSE | 14 +- client/rhel/rhn-client-tools/doc/LICENSE | 14 +- .../rhel/rhn-client-tools/src/actions/README | 90 ++++----- client/rhel/rhnlib/README | 6 +- client/rhel/rhnsd/LICENSE | 14 +- client/rhel/yum-rhn-plugin/LICENSE | 14 +- client/solaris/smartpm/LICENSE | 14 +- client/solaris/smartpm/README | 172 +++++++++--------- .../smartpm/contrib/ksmarttray/LICENSE | 14 +- client/tools/osad/LICENSE | 14 +- client/tools/rhn-virtualization/LICENSE | 14 +- client/tools/rhncfg/LICENSE | 14 +- client/tools/rhncustominfo/LICENSE | 14 +- .../spacewalk-create-channel/doc/COPYING | 14 +- .../spacewalk-create-channel/doc/README | 6 +- java/scripts/README | 8 +- projects/perl-Satcon/LICENSE | 14 +- projects/perl-Satcon/README | 4 +- projects/python-gzipstream/LICENSE | 14 +- projects/python-hwdata/LICENSE | 14 +- projects/ssl-cert-check/LICENSE | 14 +- proxy/installer/LICENSE | 14 +- proxy/proxy-docs/LICENSE | 4 +- proxy/proxy-html/LICENSE | 14 +- rel-eng/README | 64 +++---- satellite/install/README | 8 +- schema/spacewalk/README | 2 +- schema/spacewalk/postgres/README | 2 +- scripts/channel-from-system/README | 4 +- scripts/clone-errata/README | 34 ++-- scripts/ncsu-rhntools/COPYING | 14 +- scripts/ncsu-rhntools/README | 2 +- spacecmd/src/doc/README | 2 +- spacewalk/admin/LICENSE | 14 +- spacewalk/certs-tools/LICENSE | 14 +- spacewalk/config/LICENSE | 14 +- spacewalk/pylint/LICENSE | 14 +- spacewalk/setup/LICENSE | 14 +- spacewalk/spacewalk-setup-jabberd/LICENSE | 14 +- spacewalk/spacewalk-setup-postgresql/LICENSE | 14 +- web/LICENSE | 14 +- 50 files changed, 477 insertions(+), 477 deletions(-) diff --git a/LICENSE b/LICENSE index d511905c164..d159169d105 100644 --- a/LICENSE +++ b/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/backend/LICENSE b/backend/LICENSE index d511905c164..d159169d105 100644 --- a/backend/LICENSE +++ b/backend/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/backend/test/reactivation/README b/backend/test/reactivation/README index 944619cfe82..19ecb0d453a 100644 --- a/backend/test/reactivation/README +++ b/backend/test/reactivation/README @@ -1,4 +1,4 @@ 2004/05/20 jjb@redhat.com -Currently this directory contains test scripts for bug 122534. +Currently this directory contains test scripts for bug 122534. Please read the comments in reactivationTest.py for instructions on how to run the test. diff --git a/branding/LICENSE b/branding/LICENSE index d511905c164..d159169d105 100644 --- a/branding/LICENSE +++ b/branding/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/debian/packages-already-in-debian/apt-transport-spacewalk/LICENSE b/client/debian/packages-already-in-debian/apt-transport-spacewalk/LICENSE index d511905c164..d159169d105 100644 --- a/client/debian/packages-already-in-debian/apt-transport-spacewalk/LICENSE +++ b/client/debian/packages-already-in-debian/apt-transport-spacewalk/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/debian/packages-already-in-debian/python-ethtool/COPYING b/client/debian/packages-already-in-debian/python-ethtool/COPYING index a43ea2126fb..aca3fe3efe3 100644 --- a/client/debian/packages-already-in-debian/python-ethtool/COPYING +++ b/client/debian/packages-already-in-debian/python-ethtool/COPYING @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675 Mass Ave, Cambridge, MA 02139, USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - Appendix: How to Apply These Terms to Your New Programs + Appendix: How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/debian/packages-already-in-debian/rhn-client-tools/doc/LICENSE b/client/debian/packages-already-in-debian/rhn-client-tools/doc/LICENSE index d511905c164..d159169d105 100644 --- a/client/debian/packages-already-in-debian/rhn-client-tools/doc/LICENSE +++ b/client/debian/packages-already-in-debian/rhn-client-tools/doc/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/debian/packages-already-in-debian/rhn-client-tools/src/actions/README b/client/debian/packages-already-in-debian/rhn-client-tools/src/actions/README index ba9a9273e4f..109ec19cf6f 100644 --- a/client/debian/packages-already-in-debian/rhn-client-tools/src/actions/README +++ b/client/debian/packages-already-in-debian/rhn-client-tools/src/actions/README @@ -1,5 +1,5 @@ This file is to describe what actions are, how to implement them, and -how to install them. +how to install them. This is primarily concerned with the client side python code, and doesnt attempt to delve into much detail of what it takes to implement @@ -9,52 +9,52 @@ them on the up2date server side, or on the web site, or the database. 1. What are actions? - As far as the client cares, "actions" are just python -method invocation. + As far as the client cares, "actions" are just python +method invocation. 2. How do I get an action? - On the server side, actions are queued up into an -actions queue. + On the server side, actions are queued up into an +actions queue. - when rhn_check is ran, either by rhnsd, or by hand, + when rhn_check is ran, either by rhnsd, or by hand, it connections to the RHN servers, logs in, and then checks -it's action queue. +it's action queue. - If there are actions in the queue, it pops off the + If there are actions in the queue, it pops off the first one. This is done via xml-rpc encapsulated into the return of another xml-rpc call. ie: - client does: - queue.get() + client does: + queue.get() - If there are actions in the queue, this call will return + If there are actions in the queue, this call will return a string blob that is an encapsulated xml-rpc call. The reason for this is that xml-rpc represents a well understood method of representing both the method being called, and it's arguments. - The code in rhn_check unmarshals the xml-rpc blob (parses + The code in rhn_check unmarshals the xml-rpc blob (parses it into a string for methodname, and a series of data structures representing -the arguments). +the arguments). - The next step is for the client to invoke the method with the + The next step is for the client to invoke the method with the said paramaters. But first it has to find the method. The getMethod module -implements this in a fashion where methods can be stored in a -flexible hiearachy. +implements this in a fashion where methods can be stored in a +flexible hiearachy. - Once the client finds the method, it invokes it, and captures + Once the client finds the method, it invokes it, and captures it's return status. This return status is sent back to the server -via a queue.submit() call, that updates the status of the action +via a queue.submit() call, that updates the status of the action info in the database. 3. What can an action do? - Well, pretty much anything you could do with python. There + Well, pretty much anything you could do with python. There are a couple of things to keep in mind though. rhncheck runs the actions synchronously. Ie, the actions run one after another, waiting until each completes, so you may want to be careful about writing -extremely long running actions. - However, the invocaton, and the return status are done +extremely long running actions. + However, the invocaton, and the return status are done async though. Ie, the client connects, gets the action, ends the rpc, and then runs the action. It makes another rpc back to send the exit status. @@ -68,69 +68,69 @@ installed into the actions/ dir (typically /usr/share/rhn/up2date/actions) What A Module File Should Look Like - Modules exporting methods for use as actions look just like + Modules exporting methods for use as actions look just like normal python modules, with a few exceptions: - 1. There needs to be a __rhnactions__ list defined at the + 1. There needs to be a __rhnactions__ list defined at the top level of the module. The list is a list of strings of names of methods that are to be exported from the module. - 2. Filenames begining with '_' will not be elligible to -be used as actions. + 2. Filenames begining with '_' will not be elligible to +be used as actions. - This is to make it easier to write modular code without - exporting all the files you need. + This is to make it easier to write modular code without + exporting all the files you need. How to Use Classes - You can use classes inside of module files as well. A + You can use classes inside of module files as well. A few rules apply. - 1. There needs to be a __rhnactions__ list defined at + 1. There needs to be a __rhnactions__ list defined at the top level of the class. The list is a list of strings of -names of methods that are to be exported from the module. +names of methods that are to be exported from the module. - 2. The class needs to be able to run it's contructor with + 2. The class needs to be able to run it's contructor with no arguments. Since the client will need to instantiate the object, if the init for the class requires additional arguments, this will fail. - 3. the method location approach that the client takes replies + 3. the method location approach that the client takes replies on the __getattr__ method working properly. If you override the __getattr__ method, you need to make sure that the new __getattr__ can at least return -the apprroiate method names for the object. +the apprroiate method names for the object. Return Code - The proper return for an action is tuple. The + The proper return for an action is tuple. The tuple consists of: a numeric exit code a string describing what happend a "data" dictonary containing arbitrary info - that can be action specifc. + that can be action specifc. On sucess cases, the "data" dictionary can -be empty. +be empty. For failure cases, the "data" dictionary should contain at least the following fields: "version" almost always "0" but versioning is good -"name" typically of the format of methodname.errorcondtion. - (an example would be for the packges.remove action that +"name" typically of the format of methodname.errorcondtion. + (an example would be for the packges.remove action that fails because of unsolved deps "packges.remove.failed_deps") -The rest of the fields are action specific. +The rest of the fields are action specific. A success example: - return (0, "Ate Cheese Succesfully", {}) + return (0, "Ate Cheese Succesfully", {}) - return (61, "Item that claimed to be cheese was not in fact cheese", - {'name':'cheese.eat.thats_not_cheese", - 'version': '0', - 'foodstuff':'cottage cheese'}) + return (61, "Item that claimed to be cheese was not in fact cheese", + {'name':'cheese.eat.thats_not_cheese", + 'version': '0', + 'foodstuff':'cottage cheese'}) All, the error return codes are documented and registered in errstatus.txt in rhn/up2date/errstatus.txt. @@ -143,7 +143,7 @@ document there. =================================== Other Details - If you make a new directory of actions, you also need to include + If you make a new directory of actions, you also need to include an empty __init.py__ in each directory. This is neccasary for the imports to work correctly. diff --git a/client/debian/packages-already-in-debian/rhnlib/README b/client/debian/packages-already-in-debian/rhnlib/README index 446f9e06eb5..485044a7c77 100644 --- a/client/debian/packages-already-in-debian/rhnlib/README +++ b/client/debian/packages-already-in-debian/rhnlib/README @@ -8,11 +8,11 @@ This library is distributed under the terms of the GNU Public License (GPL). 0. HISTORY -Traditionally, rhn used a patched version of Fredrik Lundh's xmlrpclib, -shipped with Red Hat 6.2, 7.0, 7.1, 7.2 and 7.3 in a package called +Traditionally, rhn used a patched version of Fredrik Lundh's xmlrpclib, +shipped with Red Hat 6.2, 7.0, 7.1, 7.2 and 7.3 in a package called python-xmlrpc. -The additions included improved transport objects (proxy support, a +The additions included improved transport objects (proxy support, a better SSL framework, encodings and transfers), most of them part of a module called cgiwrap. diff --git a/client/debian/packages-already-in-debian/rhnsd/LICENSE b/client/debian/packages-already-in-debian/rhnsd/LICENSE index d511905c164..d159169d105 100644 --- a/client/debian/packages-already-in-debian/rhnsd/LICENSE +++ b/client/debian/packages-already-in-debian/rhnsd/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/rhel/rhn-client-tools/doc/LICENSE b/client/rhel/rhn-client-tools/doc/LICENSE index d511905c164..d159169d105 100644 --- a/client/rhel/rhn-client-tools/doc/LICENSE +++ b/client/rhel/rhn-client-tools/doc/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/rhel/rhn-client-tools/src/actions/README b/client/rhel/rhn-client-tools/src/actions/README index ba9a9273e4f..109ec19cf6f 100644 --- a/client/rhel/rhn-client-tools/src/actions/README +++ b/client/rhel/rhn-client-tools/src/actions/README @@ -1,5 +1,5 @@ This file is to describe what actions are, how to implement them, and -how to install them. +how to install them. This is primarily concerned with the client side python code, and doesnt attempt to delve into much detail of what it takes to implement @@ -9,52 +9,52 @@ them on the up2date server side, or on the web site, or the database. 1. What are actions? - As far as the client cares, "actions" are just python -method invocation. + As far as the client cares, "actions" are just python +method invocation. 2. How do I get an action? - On the server side, actions are queued up into an -actions queue. + On the server side, actions are queued up into an +actions queue. - when rhn_check is ran, either by rhnsd, or by hand, + when rhn_check is ran, either by rhnsd, or by hand, it connections to the RHN servers, logs in, and then checks -it's action queue. +it's action queue. - If there are actions in the queue, it pops off the + If there are actions in the queue, it pops off the first one. This is done via xml-rpc encapsulated into the return of another xml-rpc call. ie: - client does: - queue.get() + client does: + queue.get() - If there are actions in the queue, this call will return + If there are actions in the queue, this call will return a string blob that is an encapsulated xml-rpc call. The reason for this is that xml-rpc represents a well understood method of representing both the method being called, and it's arguments. - The code in rhn_check unmarshals the xml-rpc blob (parses + The code in rhn_check unmarshals the xml-rpc blob (parses it into a string for methodname, and a series of data structures representing -the arguments). +the arguments). - The next step is for the client to invoke the method with the + The next step is for the client to invoke the method with the said paramaters. But first it has to find the method. The getMethod module -implements this in a fashion where methods can be stored in a -flexible hiearachy. +implements this in a fashion where methods can be stored in a +flexible hiearachy. - Once the client finds the method, it invokes it, and captures + Once the client finds the method, it invokes it, and captures it's return status. This return status is sent back to the server -via a queue.submit() call, that updates the status of the action +via a queue.submit() call, that updates the status of the action info in the database. 3. What can an action do? - Well, pretty much anything you could do with python. There + Well, pretty much anything you could do with python. There are a couple of things to keep in mind though. rhncheck runs the actions synchronously. Ie, the actions run one after another, waiting until each completes, so you may want to be careful about writing -extremely long running actions. - However, the invocaton, and the return status are done +extremely long running actions. + However, the invocaton, and the return status are done async though. Ie, the client connects, gets the action, ends the rpc, and then runs the action. It makes another rpc back to send the exit status. @@ -68,69 +68,69 @@ installed into the actions/ dir (typically /usr/share/rhn/up2date/actions) What A Module File Should Look Like - Modules exporting methods for use as actions look just like + Modules exporting methods for use as actions look just like normal python modules, with a few exceptions: - 1. There needs to be a __rhnactions__ list defined at the + 1. There needs to be a __rhnactions__ list defined at the top level of the module. The list is a list of strings of names of methods that are to be exported from the module. - 2. Filenames begining with '_' will not be elligible to -be used as actions. + 2. Filenames begining with '_' will not be elligible to +be used as actions. - This is to make it easier to write modular code without - exporting all the files you need. + This is to make it easier to write modular code without + exporting all the files you need. How to Use Classes - You can use classes inside of module files as well. A + You can use classes inside of module files as well. A few rules apply. - 1. There needs to be a __rhnactions__ list defined at + 1. There needs to be a __rhnactions__ list defined at the top level of the class. The list is a list of strings of -names of methods that are to be exported from the module. +names of methods that are to be exported from the module. - 2. The class needs to be able to run it's contructor with + 2. The class needs to be able to run it's contructor with no arguments. Since the client will need to instantiate the object, if the init for the class requires additional arguments, this will fail. - 3. the method location approach that the client takes replies + 3. the method location approach that the client takes replies on the __getattr__ method working properly. If you override the __getattr__ method, you need to make sure that the new __getattr__ can at least return -the apprroiate method names for the object. +the apprroiate method names for the object. Return Code - The proper return for an action is tuple. The + The proper return for an action is tuple. The tuple consists of: a numeric exit code a string describing what happend a "data" dictonary containing arbitrary info - that can be action specifc. + that can be action specifc. On sucess cases, the "data" dictionary can -be empty. +be empty. For failure cases, the "data" dictionary should contain at least the following fields: "version" almost always "0" but versioning is good -"name" typically of the format of methodname.errorcondtion. - (an example would be for the packges.remove action that +"name" typically of the format of methodname.errorcondtion. + (an example would be for the packges.remove action that fails because of unsolved deps "packges.remove.failed_deps") -The rest of the fields are action specific. +The rest of the fields are action specific. A success example: - return (0, "Ate Cheese Succesfully", {}) + return (0, "Ate Cheese Succesfully", {}) - return (61, "Item that claimed to be cheese was not in fact cheese", - {'name':'cheese.eat.thats_not_cheese", - 'version': '0', - 'foodstuff':'cottage cheese'}) + return (61, "Item that claimed to be cheese was not in fact cheese", + {'name':'cheese.eat.thats_not_cheese", + 'version': '0', + 'foodstuff':'cottage cheese'}) All, the error return codes are documented and registered in errstatus.txt in rhn/up2date/errstatus.txt. @@ -143,7 +143,7 @@ document there. =================================== Other Details - If you make a new directory of actions, you also need to include + If you make a new directory of actions, you also need to include an empty __init.py__ in each directory. This is neccasary for the imports to work correctly. diff --git a/client/rhel/rhnlib/README b/client/rhel/rhnlib/README index b46c6f32365..12b96a4cff9 100644 --- a/client/rhel/rhnlib/README +++ b/client/rhel/rhnlib/README @@ -8,11 +8,11 @@ This library is distributed under the terms of the GNU Public License (GPL). 0. HISTORY -Traditionally, rhn used a patched version of Fredrik Lundh's xmlrpclib, -shipped with Red Hat 6.2, 7.0, 7.1, 7.2 and 7.3 in a package called +Traditionally, rhn used a patched version of Fredrik Lundh's xmlrpclib, +shipped with Red Hat 6.2, 7.0, 7.1, 7.2 and 7.3 in a package called python-xmlrpc. -The additions included improved transport objects (proxy support, a +The additions included improved transport objects (proxy support, a better SSL framework, encodings and transfers), most of them part of a module called cgiwrap. diff --git a/client/rhel/rhnsd/LICENSE b/client/rhel/rhnsd/LICENSE index d511905c164..d159169d105 100644 --- a/client/rhel/rhnsd/LICENSE +++ b/client/rhel/rhnsd/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/rhel/yum-rhn-plugin/LICENSE b/client/rhel/yum-rhn-plugin/LICENSE index d511905c164..d159169d105 100644 --- a/client/rhel/yum-rhn-plugin/LICENSE +++ b/client/rhel/yum-rhn-plugin/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/solaris/smartpm/LICENSE b/client/solaris/smartpm/LICENSE index 5b6e7c66c27..db2fc4505d2 100644 --- a/client/solaris/smartpm/LICENSE +++ b/client/solaris/smartpm/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/solaris/smartpm/README b/client/solaris/smartpm/README index adbd07cfc75..922ffdee5c9 100644 --- a/client/solaris/smartpm/README +++ b/client/solaris/smartpm/README @@ -229,28 +229,28 @@ on the interface in use and on the intended goal. The following command would install the `foobar` package, for instance:: - smart install foobar + smart install foobar While the following command would install the `foobar` package, but with graphic output:: - smart --gui install foobar + smart --gui install foobar To open the graphic interface in interactive mode, one may simply run:: - smart --gui + smart --gui Similarly, the following command would open the shell interface:: - smart --shell + smart --shell Extensive help is available for all commands, by using the `--help` switch:: - smart --help - smart install --help - smart channel --help - ... + smart --help + smart install --help + smart channel --help + ... -------------- Building Smart @@ -260,31 +260,31 @@ Dependencies ------------ :Core: - Smart is written in Python, with some core modules rewritten as - C extensions for memory savings and performance gains. With that - in mind, the core system of Smart depends on Python 2.3 or - higher, and a C compiler to build the extensions. + Smart is written in Python, with some core modules rewritten as + C extensions for memory savings and performance gains. With that + in mind, the core system of Smart depends on Python 2.3 or + higher, and a C compiler to build the extensions. :Graphic Interface: - The graphic interface depends on `pygtk` 2.4 or higher. + The graphic interface depends on `pygtk` 2.4 or higher. :RPM backend: - The RPM backend depends on the Python `rpm` module of RPM 4.4 or - higher, due to a limitation which was present in previous versions - of the `ts.dbMatch()` method, and the availability of the - `readHeaderFromFD()` function. + The RPM backend depends on the Python `rpm` module of RPM 4.4 or + higher, due to a limitation which was present in previous versions + of the `ts.dbMatch()` method, and the availability of the + `readHeaderFromFD()` function. - In the `contrib/patches/` subdirectory there are patches for - previous RPM versions including the missing functionality. There - are also pre-packaged binary versions which include the patched - module without requiring changes in other tools. + In the `contrib/patches/` subdirectory there are patches for + previous RPM versions including the missing functionality. There + are also pre-packaged binary versions which include the patched + module without requiring changes in other tools. :DPKG backend: - There are no extra dependencies besides DPKG itself. + There are no extra dependencies besides DPKG itself. :Slackware backend: - There are no extra dependencies besides the packaging scripts - `installpkg`, `upgradepkg` and `removepkg`. + There are no extra dependencies besides the packaging scripts + `installpkg`, `upgradepkg` and `removepkg`. ------------ Case Studies @@ -316,12 +316,12 @@ The problem starts when an installation of `xscreensaver` is tried:: requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. - + Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: - + The following packages have unmet dependencies: xscreensaver: Depends: libglade-2.0.so.0 Depends: libxml2.so.2 @@ -337,12 +337,12 @@ The error shown makes the user belive that `libglade-2.0.so.0` and requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. - + Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: - + The following packages have unmet dependencies: libxml2: Depends: glibc-iconv but it is not going to be installed E: Broken packages @@ -356,12 +356,12 @@ Another misguiding error message. Let's go further:: requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. - + Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: - + The following packages have unmet dependencies: glibc-iconv: Depends: glibc-gconvdata (= 2.3.3) but 1:2.3.2-586_1cl is to be installed E: Broken packages @@ -391,12 +391,12 @@ expected result is obtained:: [root@damien:/root] smart install xscreensaver Updating cache... ######################################## [100%] - + Computing transaction... - + Downgrading packages (1): glibc-gconvdata-0:2.3.3-69473cl.i386 - + Installed packages (4): glibc-iconv-0:2.3.3-69473cl.i386 libglade2-2.4.0-68154cl.i386 @@ -464,11 +464,11 @@ First, let's see how YUM deals with the problem:: BCD-1.0-1cl.i386.rpm 100% |=========================| 1.0 kB 00:00 ---> Package BCD.i386 0:1.0-1cl set to be installed --> Running transaction check - + Dependencies Resolved Transaction Listing: Install: A.i386 0:1.0-1cl - + Performing the following to resolve dependencies: Install: B.i386 0:1.0-1cl Install: BCD.i386 0:1.0-1cl @@ -501,14 +501,14 @@ Now, let's see how Smart would solve the problem:: [root@burma ~]% smart install A Updating cache... ######################################## [100%] - + Computing transaction... - + Installed packages (2): A-1.0-1cl@i386 BCD-1.0-1cl@i386 - + 2.7kb of package files are needed. - + Confirm changes (Y/n)? Smart correctly selected only `BCD`, since it's necessary anyway, and @@ -549,12 +549,12 @@ What happens when forcing APT to install `A`:: requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. - + Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: - + The following packages have unmet dependencies: A: Depends: B but it is not installable E: Broken packages @@ -597,14 +597,14 @@ Now, let's see how Smart would behave in the same situation:: [root@burma ~]% smart upgrade Loading cache... Updating cache... ######################################## [100%] - + Computing transaction... - + Upgrading packages (1): A-1.5-1cl@i386 - + 1.3kb of package files are needed. - + Confirm changes (Y/n)? Smart correctly selects the intermediate version 1.5, which is the @@ -642,17 +642,17 @@ Let's see Smart in the same situation:: [root@burma ~]% smart upgrade Loading cache... Updating cache... ######################################## [100%] - + Computing transaction... - + Upgrading packages (1): B-2.0-1cl@i386 - + Installed packages (1): C-2.0-1cl@i386 - + 2.6kB of package files are needed. - + Confirm changes (Y/n)? Smart correctly selected package `C` for installation as a viable @@ -667,68 +667,68 @@ This is the credit section, where people and institutions that have somehow contributed to the project are mentioned. :Conectiva, Inc.: - Conectiva has funded Smart development as the author's employer. + Conectiva has funded Smart development as the author's employer. :Wanderlei Cavassin: - Conectiva's research & development coordinator, who belived - the project was viable and encouraged the author to work on it. + Conectiva's research & development coordinator, who belived + the project was viable and encouraged the author to work on it. :Ednilson Miura & Herton Ronaldo Krzesinski: - Conectiva employees, helped setting up many distributions - for tests whenever necessary. + Conectiva employees, helped setting up many distributions + for tests whenever necessary. :Andreas Hasenack: - Conectiva employee, helped as being the first brave pre-alpha - tester, and contributed with many ideas, discussions, etc. + Conectiva employee, helped as being the first brave pre-alpha + tester, and contributed with many ideas, discussions, etc. :Arnaldo Carvalho de Melo: - Conectiva board member, helped with the "channel of mirrors" idea - and by encouraging the author to build a generic channel - information method. + Conectiva board member, helped with the "channel of mirrors" idea + and by encouraging the author to build a generic channel + information method. :Others @ Conectiva: - Many other people in Conectiva helped with ideas and - alpha-testing in general during the pre-release period of - Smart development. + Many other people in Conectiva helped with ideas and + alpha-testing in general during the pre-release period of + Smart development. :Guilerme Manika & Ruda Moura: - Ancient Conectiva employees, now board members of the Haxent company, - helped by testing Smart extensively in Fedora, reporting many - bugs and suggesting changes. They have also created the Smart - FAQ_. + Ancient Conectiva employees, now board members of the Haxent company, + helped by testing Smart extensively in Fedora, reporting many + bugs and suggesting changes. They have also created the Smart + FAQ_. :APT-RPM & Debian: - Experience on packaging and ideas for a better framework were - developed while the author of Smart worked as the `APT-RPM` - maintainer. + Experience on packaging and ideas for a better framework were + developed while the author of Smart worked as the `APT-RPM` + maintainer. :Jeff Johnson: - Maintainer of the `RPM` software, employed by RedHat, Inc. - contributed as being the RPM maintainer itself, and in - many discussions regarding packaging theory in general. + Maintainer of the `RPM` software, employed by RedHat, Inc. + contributed as being the RPM maintainer itself, and in + many discussions regarding packaging theory in general. :Seth Vidal: - YUM author, and member of the Duke University, contributed - to Smart with the development of the XML `MetaData` repository - format and discussions about it. + YUM author, and member of the Duke University, contributed + to Smart with the development of the XML `MetaData` repository + format and discussions about it. :Michael Vogt: - Co-maintainer of the Synaptic project (*the* maintainer, lately), - contributed by discussing ideas that could be/were implemented - in Synaptic, and ended up being adopted by Smart as well. + Co-maintainer of the Synaptic project (*the* maintainer, lately), + contributed by discussing ideas that could be/were implemented + in Synaptic, and ended up being adopted by Smart as well. :Sebastian Heinlein: - Author of the package icons for Synaptic, that were mercilessly - stolen to be used in Smart's graphic interface. + Author of the package icons for Synaptic, that were mercilessly + stolen to be used in Smart's graphic interface. :TaQ/PiterPunk at #slackware-br: - These guys helped Smart development by explaining details of - Slackware practices regarding packaging. + These guys helped Smart development by explaining details of + Slackware practices regarding packaging. :Matt Zimmerman: - Debian/Ubuntu developer and co-maintainer of the APT software, - helped by shining some light regarding details of the `DPKG` - pre-depends ordering expectations. + Debian/Ubuntu developer and co-maintainer of the APT software, + helped by shining some light regarding details of the `DPKG` + pre-depends ordering expectations. .. _FAQ: http://zorked.net/smart/FAQ.html diff --git a/client/solaris/smartpm/contrib/ksmarttray/LICENSE b/client/solaris/smartpm/contrib/ksmarttray/LICENSE index 5b6e7c66c27..db2fc4505d2 100644 --- a/client/solaris/smartpm/contrib/ksmarttray/LICENSE +++ b/client/solaris/smartpm/contrib/ksmarttray/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/tools/osad/LICENSE b/client/tools/osad/LICENSE index d511905c164..d159169d105 100644 --- a/client/tools/osad/LICENSE +++ b/client/tools/osad/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/tools/rhn-virtualization/LICENSE b/client/tools/rhn-virtualization/LICENSE index d511905c164..d159169d105 100644 --- a/client/tools/rhn-virtualization/LICENSE +++ b/client/tools/rhn-virtualization/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/tools/rhncfg/LICENSE b/client/tools/rhncfg/LICENSE index d511905c164..d159169d105 100644 --- a/client/tools/rhncfg/LICENSE +++ b/client/tools/rhncfg/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/tools/rhncustominfo/LICENSE b/client/tools/rhncustominfo/LICENSE index d511905c164..d159169d105 100644 --- a/client/tools/rhncustominfo/LICENSE +++ b/client/tools/rhncustominfo/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/tools/spacewalk-remote-utils/spacewalk-create-channel/doc/COPYING b/client/tools/spacewalk-remote-utils/spacewalk-create-channel/doc/COPYING index d60c31a97a5..a3e97747969 100644 --- a/client/tools/spacewalk-remote-utils/spacewalk-create-channel/doc/COPYING +++ b/client/tools/spacewalk-remote-utils/spacewalk-create-channel/doc/COPYING @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/client/tools/spacewalk-remote-utils/spacewalk-create-channel/doc/README b/client/tools/spacewalk-remote-utils/spacewalk-create-channel/doc/README index c4beae056be..ed3d53f930b 100644 --- a/client/tools/spacewalk-remote-utils/spacewalk-create-channel/doc/README +++ b/client/tools/spacewalk-remote-utils/spacewalk-create-channel/doc/README @@ -1,5 +1,5 @@ spacewalk-create-channel - by Justin Sherrill (jsherril@redhat.com) + by Justin Sherrill (jsherril@redhat.com) This script can create a channel to a specific update level (i.e. RHEL4u3) or upgrade an existing channel to a higher update level on an Red Hat Satellite or Spacewalk server. @@ -33,7 +33,7 @@ kernel-smp bash then simply pass the '--skiplist=skiplist.txt' option when running the command. All packages from the specified release will - be copied to the channel except for those in the skip list. + be copied to the channel except for those in the skip list. In addition to the script, you should find in this package: @@ -62,7 +62,7 @@ Changelog: - added --skiplist option for a package skiplist 03/06/09 - 2.0-beta -- Rewrite in python, supporting command line arguments. +- Rewrite in python, supporting command line arguments. - Now support clearing channel (with --clear) before pushing packages - Can now specify the src channel if you don't want to the script to figure it out - Can now just specify the data file instead of version, release, arch, etc.. diff --git a/java/scripts/README b/java/scripts/README index 2eef6c9701b..2b69c4effcf 100644 --- a/java/scripts/README +++ b/java/scripts/README @@ -9,9 +9,9 @@ create-api-test - creates python xmlrpc api testcase dumpnavtree.sh - dumps the nav tree given a nav*.xml file gen-eclipse.py - generates eclipse .classpath file (should be renamed) jarsearch.sh - searches a directory of jars for a specific class -java-create-page.pl - -java-map-hibernate-table.pl - -java-xliff-csv.pl - +java-create-page.pl - +java-map-hibernate-table.pl - +java-xliff-csv.pl - loadnouser.pl - multithreaded load test for rhn with NO user lwload.pl - multithreaded load test for rhn maketar.sh - creates a tarball of the rhn-java code for use in building @@ -20,7 +20,7 @@ refreshi18n.sh - ??? refreshRHNdocs.sh - ??? sat-scrub.pl - scrubs a satellite test db slocc.sh - counts lines of code, comments, and prints their ratios -taskomatic - +taskomatic - unnecessaryElse.pl - removes unnecessary else blocks from java files. unreadField.pl - removes unused private member varialbes from java files. unusedLocal.pl - removes unused local variables from java files. diff --git a/projects/perl-Satcon/LICENSE b/projects/perl-Satcon/LICENSE index d511905c164..d159169d105 100644 --- a/projects/perl-Satcon/LICENSE +++ b/projects/perl-Satcon/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/projects/perl-Satcon/README b/projects/perl-Satcon/README index e1912f67daa..2c5a40aa599 100644 --- a/projects/perl-Satcon/README +++ b/projects/perl-Satcon/README @@ -1,7 +1,7 @@ Satcon =================== -This is framework for reading configuration files templates +This is framework for reading configuration files templates in format: key[prompt]=question key=value @@ -17,7 +17,7 @@ To install this module type the following: COPYRIGHT AND LICENCE -Copyright (C) 2008 Red Hat, Inc. +Copyright (C) 2008 Red Hat, Inc. This software is licensed to you under the GNU General Public License, version 2 (GPLv2). There is NO WARRANTY for this software, express or diff --git a/projects/python-gzipstream/LICENSE b/projects/python-gzipstream/LICENSE index d511905c164..d159169d105 100644 --- a/projects/python-gzipstream/LICENSE +++ b/projects/python-gzipstream/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/projects/python-hwdata/LICENSE b/projects/python-hwdata/LICENSE index d511905c164..d159169d105 100644 --- a/projects/python-hwdata/LICENSE +++ b/projects/python-hwdata/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/projects/ssl-cert-check/LICENSE b/projects/ssl-cert-check/LICENSE index d511905c164..d159169d105 100644 --- a/projects/ssl-cert-check/LICENSE +++ b/projects/ssl-cert-check/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/proxy/installer/LICENSE b/proxy/installer/LICENSE index d511905c164..d159169d105 100644 --- a/proxy/installer/LICENSE +++ b/proxy/installer/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/proxy/proxy-docs/LICENSE b/proxy/proxy-docs/LICENSE index ae6765b0a87..e6f4b11ecce 100644 --- a/proxy/proxy-docs/LICENSE +++ b/proxy/proxy-docs/LICENSE @@ -41,7 +41,7 @@ All modified versions of documents covered by this license, including translatio 2. The person making the modifications must be identified and the modifications dated. 3. Acknowledgement of the original author and publisher if applicable must be retained according to normal academic citation practices. 4. The location of the original unmodified document must be identified. - 5. The original author's (or authors') name(s) may not be used to assert or imply endorsement of the resulting document without the original author's (or authors') permission. + 5. The original author's (or authors') name(s) may not be used to assert or imply endorsement of the resulting document without the original author's (or authors') permission. V. GOOD-PRACTICE RECOMMENDATIONS @@ -50,7 +50,7 @@ In addition to the requirements of this license, it is requested from and strong 1. If you are distributing Open Publication works on hardcopy or CD-ROM, you provide email notification to the authors of your intent to redistribute at least thirty days before your manuscript or media freeze, to give the authors time to provide updated documents. This notification should describe modifications, if any, made to the document. 2. All substantive modifications (including deletions) be either clearly marked up in the document or else described in an attachment to the document. - 3. Finally, while it is not mandatory under this license, it is considered good form to offer a free copy of any hardcopy and CD-ROM expression of an Open Publication-licensed work to its author(s). + 3. Finally, while it is not mandatory under this license, it is considered good form to offer a free copy of any hardcopy and CD-ROM expression of an Open Publication-licensed work to its author(s). VI. LICENSE OPTIONS diff --git a/proxy/proxy-html/LICENSE b/proxy/proxy-html/LICENSE index d511905c164..d159169d105 100644 --- a/proxy/proxy-html/LICENSE +++ b/proxy/proxy-html/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/rel-eng/README b/rel-eng/README index e9624008252..03d01c98e2b 100644 --- a/rel-eng/README +++ b/rel-eng/README @@ -1,25 +1,25 @@ Usage: - make tag-release Bump version of the package and tag the commit. + make tag-release Bump version of the package and tag the commit. - make tag-minor-release Bump release of the package and tag the commit. + make tag-minor-release Bump release of the package and tag the commit. - After running make tag-release or tag-minor-release, the tag is - only in your local repository. Review the changes - (try: gitk --all &) and then push the commit and the new tag to - the upstream repository, or make srpm will use the old tag (or - not work at all): + After running make tag-release or tag-minor-release, the tag is + only in your local repository. Review the changes + (try: gitk --all &) and then push the commit and the new tag to + the upstream repository, or make srpm will use the old tag (or + not work at all): - git push - git push ssh://git.fedorahosted.org/git/spacewalk.git/ tag + git push + git push ssh://git.fedorahosted.org/git/spacewalk.git/ tag - make srpm Build .src.rpm from latest tagged release of the - package. The tag has to be not only in the local - repository but also in the upstream repo. + make srpm Build .src.rpm from latest tagged release of the + package. The tag has to be not only in the local + repository but also in the upstream repo. - The srpm target understands one parameter, DIST. Use it to build - .src.rpm with this %{dist} instead of your own, to match whatever - your build system expects. Do not forget the leading dot. Example: - make srpm DIST=.el5.sw + The srpm target understands one parameter, DIST. Use it to build + .src.rpm with this %{dist} instead of your own, to match whatever + your build system expects. Do not forget the leading dot. Example: + make srpm DIST=.el5.sw make tgz Create the tar.gz for the latest tagged release of the package. @@ -34,38 +34,38 @@ Usage: user make test-srpm Packs source from local HEAD and builds srpm locally. - You can then rpmbuild it on your machine or - elsewhere. The package has git commit SHA1 in its - Release. The .src.rpm will be left in your working - directory. + You can then rpmbuild it on your machine or + elsewhere. The package has git commit SHA1 in its + Release. The .src.rpm will be left in your working + directory. make test-rpm Packs source from local HEAD and builds both srpm - and binary rpm locally. The package has git commit - SHA1 in its Release. The .src.rpm will be left in - your working directory, the .rpm(s) in some noarch - or arch subdirectories. + and binary rpm locally. The package has git commit + SHA1 in its Release. The .src.rpm will be left in + your working directory, the .rpm(s) in some noarch + or arch subdirectories. - The Makefile.git includes file ~/.spacewalk-build-rc if it exists. - You might want to put line like - RPMBUILD_BASEDIR = /tmp/spacewalk-build - there, the path pointing to directory where builds will take place - and where .rpm will land (instead of your working tree). + The Makefile.git includes file ~/.spacewalk-build-rc if it exists. + You might want to put line like + RPMBUILD_BASEDIR = /tmp/spacewalk-build + there, the path pointing to directory where builds will take place + and where .rpm will land (instead of your working tree). The Makefile in package's directory should specify NAME and SPECFILE, and then include this Makefile, via - include .../rel-eng/Makefile + include .../rel-eng/Makefile If you do not want the directory to be packed to .tar.gz for packages where we are not the upstream, specify - NO_TAR_GZ = 1 + NO_TAR_GZ = 1 in the Makefile. In that case, you need to have that upstream's .tar.gz in the repository already. If you want some sources to be downloaded from external URIs, specify - DOWNLOAD_SOURCES = http://www.example.com/path/source-1.2.3.tar.gz + DOWNLOAD_SOURCES = http://www.example.com/path/source-1.2.3.tar.gz in the Makefile, and the URL will be fetched via wget upon make (test-)srpm. diff --git a/satellite/install/README b/satellite/install/README index 4cfefe73a64..2c9ebfd4fa9 100644 --- a/satellite/install/README +++ b/satellite/install/README @@ -15,8 +15,8 @@ INSTALLATION METHODS - BASIC USAGE There are two methods of installing Satellite. -1) You may run the 'install.pl' script, which will prompt you for answers to -several questions necessary for configuring Satellite. You can do this by simply +1) You may run the 'install.pl' script, which will prompt you for answers to +several questions necessary for configuring Satellite. You can do this by simply typing (as root): ./install.pl @@ -35,7 +35,7 @@ you can run the installer like so: ./install.pl --answer-file= -Where is the location of the answerfile, for example, +Where is the location of the answerfile, for example, '/tmp/answers.txt'. This installation method is useful if you would like to install multiple @@ -73,7 +73,7 @@ Documentation Full Satellite documentation in PDF and HTML formats is provided at: http://www.redhat.com/docs/manuals/satellite/ - + Of particular interest would be the Installation Guide. Customer Service diff --git a/schema/spacewalk/README b/schema/spacewalk/README index ca30b2ea66e..55a49afda0a 100644 --- a/schema/spacewalk/README +++ b/schema/spacewalk/README @@ -3,7 +3,7 @@ DIRECTORIES ------------------------------------------------------------------------------- -/schema/spacewalk +/schema/spacewalk /schema/spacewalk/common - Common DDL /schema/spacewalk/common/tables - Common DDL: table,index,sequences /schema/spacewalk/common/data - Common SQL: INSERTs diff --git a/schema/spacewalk/postgres/README b/schema/spacewalk/postgres/README index fb59edcdfe2..b072496e1ac 100644 --- a/schema/spacewalk/postgres/README +++ b/schema/spacewalk/postgres/README @@ -1,6 +1,6 @@ Load postgresql schema using main.sql, run from the postgresql directory: - psql -d spacewalk -f main.sql -q -v ON_ERROR_STOP= + psql -d spacewalk -f main.sql -q -v ON_ERROR_STOP= And to cleanup the database, use a combination of drop + create, like so: diff --git a/scripts/channel-from-system/README b/scripts/channel-from-system/README index 041719963c3..7b22ecf1252 100644 --- a/scripts/channel-from-system/README +++ b/scripts/channel-from-system/README @@ -1,6 +1,6 @@ Create channel from system script - by Justin Sherrill (jsherril@redhat.com) + by Justin Sherrill (jsherril@redhat.com) -This script takes in a package list of a system (from a sysreport for example) and creates a base channel from it. +This script takes in a package list of a system (from a sysreport for example) and creates a base channel from it. For help, simply run ./create-channel-from-system.pl --help diff --git a/scripts/clone-errata/README b/scripts/clone-errata/README index 8076ed22b8a..ebb41be7bcd 100644 --- a/scripts/clone-errata/README +++ b/scripts/clone-errata/README @@ -6,9 +6,9 @@ The script self-documents as much as possible. Typical usage would be something like this: rhn-clone-errata.py -f /root/.rhnscript \ - -c rhel-x86_64-server-6 \ - -b `date +"\%Y\%m\%d" -d "-1 week"` \ - -i + -c rhel-x86_64-server-6 \ + -b `date +"\%Y\%m\%d" -d "-1 week"` \ + -i usage: rhn-clone-errata.py [options] @@ -36,13 +36,13 @@ options: -e EDATE, --end-date=EDATE Ending Date: ie. "19001231" (defaults to TODAY) -i, --publish Publish Errata (into destination channels) - -I, --ignoremissing Default behavior is to skip errata for which - there are missing packages, this option - allows the errata to be created without - packages that it should have. + -I, --ignoremissing Default behavior is to skip errata for which + there are missing packages, this option + allows the errata to be created without + packages that it should have. -A, --sync-all-channels - This option clones errata for all channels - configured in the config file. + This option clones errata for all channels + configured in the config file. -x PROXY, --proxy=PROXY Proxy server and port to use (e.g. proxy.company.com:3128) @@ -58,14 +58,14 @@ options: 2011/09/06 - Andy Speagle - I'm presently working on adding in support for CVEs - but am running into an issue. Probably done in - version 1.6 ... + I'm presently working on adding in support for CVEs + but am running into an issue. Probably done in + version 1.6 ... 2011/11/17 - Andy speagle - Default behavior of how errata with missing packages - are handled has been changed. If an errata is missing - packages, the script will now, by default, skip creating - that errata. You can use "-I" to ignore missing packages - and continue creating the errata. + Default behavior of how errata with missing packages + are handled has been changed. If an errata is missing + packages, the script will now, by default, skip creating + that errata. You can use "-I" to ignore missing packages + and continue creating the errata. diff --git a/scripts/ncsu-rhntools/COPYING b/scripts/ncsu-rhntools/COPYING index d60c31a97a5..a3e97747969 100644 --- a/scripts/ncsu-rhntools/COPYING +++ b/scripts/ncsu-rhntools/COPYING @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/scripts/ncsu-rhntools/README b/scripts/ncsu-rhntools/README index d60a051fb72..f38439fe015 100644 --- a/scripts/ncsu-rhntools/README +++ b/scripts/ncsu-rhntools/README @@ -20,7 +20,7 @@ be used with subscribeRHN.py. subscribeRHN.py - Re-subscribe machines in RHN to needed sub-channels when the RHN contract expires or whathaveyou. -groupSummary.py - Displays a summary of the RHN groups and ungrouped +groupSummary.py - Displays a summary of the RHN groups and ungrouped machines. oldSystems.py - Delete registrations that have been inactive for X diff --git a/spacecmd/src/doc/README b/spacecmd/src/doc/README index 9d17b13e765..efdce21c2e7 100644 --- a/spacecmd/src/doc/README +++ b/spacecmd/src/doc/README @@ -83,7 +83,7 @@ spacecmd> report_ipaddresses System Hostname IP ------ -------- -- dns01 dns01.dmz.example.com 192.168.254.53 -www01 www01.dmz.example.com 192.168.254.80 +www01 www01.dmz.example.com 192.168.254.80 ztest ztest.test.example.com 192.168.42.111 spacecmd> report_kernels diff --git a/spacewalk/admin/LICENSE b/spacewalk/admin/LICENSE index d511905c164..d159169d105 100644 --- a/spacewalk/admin/LICENSE +++ b/spacewalk/admin/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/spacewalk/certs-tools/LICENSE b/spacewalk/certs-tools/LICENSE index d511905c164..d159169d105 100644 --- a/spacewalk/certs-tools/LICENSE +++ b/spacewalk/certs-tools/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/spacewalk/config/LICENSE b/spacewalk/config/LICENSE index d511905c164..d159169d105 100644 --- a/spacewalk/config/LICENSE +++ b/spacewalk/config/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/spacewalk/pylint/LICENSE b/spacewalk/pylint/LICENSE index d511905c164..d159169d105 100644 --- a/spacewalk/pylint/LICENSE +++ b/spacewalk/pylint/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/spacewalk/setup/LICENSE b/spacewalk/setup/LICENSE index d511905c164..d159169d105 100644 --- a/spacewalk/setup/LICENSE +++ b/spacewalk/setup/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/spacewalk/spacewalk-setup-jabberd/LICENSE b/spacewalk/spacewalk-setup-jabberd/LICENSE index d511905c164..d159169d105 100644 --- a/spacewalk/spacewalk-setup-jabberd/LICENSE +++ b/spacewalk/spacewalk-setup-jabberd/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/spacewalk/spacewalk-setup-postgresql/LICENSE b/spacewalk/spacewalk-setup-postgresql/LICENSE index d511905c164..d159169d105 100644 --- a/spacewalk/spacewalk-setup-postgresql/LICENSE +++ b/spacewalk/spacewalk-setup-postgresql/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it diff --git a/web/LICENSE b/web/LICENSE index d511905c164..d159169d105 100644 --- a/web/LICENSE +++ b/web/LICENSE @@ -1,12 +1,12 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. - Preamble + Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public @@ -56,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. - GNU GENERAL PUBLIC LICENSE + GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains @@ -255,7 +255,7 @@ make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. - NO WARRANTY + NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN @@ -277,9 +277,9 @@ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. - END OF TERMS AND CONDITIONS + END OF TERMS AND CONDITIONS - How to Apply These Terms to Your New Programs + How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it