Gentoo Archives: gentoo-commits

From: "Michał Górny" <mgorny@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apps/phpwebsite/, profiles/, www-apps/phpwebsite/files/
Date: Mon, 23 Sep 2019 07:21:31
Message-Id: 1569223186.2f8ff0948761fef75e3a38a0a918ba869779a4a5.mgorny@gentoo
1 commit: 2f8ff0948761fef75e3a38a0a918ba869779a4a5
2 Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
3 AuthorDate: Mon Sep 23 07:19:46 2019 +0000
4 Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
5 CommitDate: Mon Sep 23 07:19:46 2019 +0000
6 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2f8ff094
7
8 www-apps/phpwebsite: Remove last-rited pkg
9
10 Closes: https://bugs.gentoo.org/651166
11 Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
12
13 profiles/package.mask | 3 +-
14 www-apps/phpwebsite/Manifest | 1 -
15 www-apps/phpwebsite/files/postinstall-en.txt | 130 ---------------------------
16 www-apps/phpwebsite/metadata.xml | 12 ---
17 www-apps/phpwebsite/phpwebsite-1.7.2.ebuild | 43 ---------
18 5 files changed, 1 insertion(+), 188 deletions(-)
19
20 diff --git a/profiles/package.mask b/profiles/package.mask
21 index 10340ca1868..57ef0be7a53 100644
22 --- a/profiles/package.mask
23 +++ b/profiles/package.mask
24 @@ -1160,9 +1160,8 @@ sys-cluster/open-mx
25 # These packages are incompatible with current versions of PHP (7 or higher)
26 # They need a maintainer but no one has volunteered.
27 # Removal in 30 days if no one picks them up.
28 -# Bugs 615472 and 651166 respectively
29 +# Bug 615472
30 www-apps/groupoffice
31 -www-apps/phpwebsite
32
33 # Miroslav Šulc <fordfrog@g.o> (2019-08-19)
34 # Depends on >=virtual/{jdk,jre}-11 which is masked
35
36 diff --git a/www-apps/phpwebsite/Manifest b/www-apps/phpwebsite/Manifest
37 deleted file mode 100644
38 index 03fa9d041a0..00000000000
39 --- a/www-apps/phpwebsite/Manifest
40 +++ /dev/null
41 @@ -1 +0,0 @@
42 -DIST phpwebsite_1_7_2.tar.gz 14531036 BLAKE2B 4681cad72ebc9ae3e1838b0db15022a8681560dae27bd9cc4be9e1b4b1d479e218e43781e2c5024924c762cbc85eacfa31ab975ab81587e42356bbb0b7936c9f SHA512 cf3f503794bb12d24ea003b0caf3e98148be43e0acd38e4d15be559cdf643266270800450309337d6540eaa069022730cef64bf315bd0fb3853a344a63c78ae5
43
44 diff --git a/www-apps/phpwebsite/files/postinstall-en.txt b/www-apps/phpwebsite/files/postinstall-en.txt
45 deleted file mode 100644
46 index 7bca5583daf..00000000000
47 --- a/www-apps/phpwebsite/files/postinstall-en.txt
48 +++ /dev/null
49 @@ -1,130 +0,0 @@
50 -phpWebSite is installed.
51 -
52 -Installation Instructions
53 -=========================
54 -
55 -You will need to create a database for phpWebSite
56 -on your own before starting setup.
57 -
58 -Then change permissions for set with this script:
59 -
60 -cd ${MY_INSTALLDIR}/setup
61 -./secure_phpws.sh setup
62 -
63 -Once you have a database ready proceed to
64 -http://${VHOST_HOSTNAME}/${VHOST_APPDIR} to continue installation.
65 -
66 -Once you are done with installation you need to run:
67 -
68 -cd ${MY_INSTALLDIR}/setup
69 -./secure_phpws.sh run apache users
70 -
71 -Upgrade Instructions
72 -====================
73 -
74 -Preparing to Upgrade
75 ---------------------
76 - - Dump/backup your hub and branch databases.
77 - - Backup your hub and branch directories/files.
78 - - Create an index.php file that warns users of the upgrade.
79 -
80 -<?php
81 -echo "<div align=\"center\"><h1>Please be patient while we upgrade the site.</h1>
82 -We'll be back in a jiffy!</div>";
83 -?>
84 -
85 - - Close and restart your browser. If you have a session live while updating
86 - your site, it MIGHT interfere with the upgrade process. If you are using
87 - Boost to upgrade, you can skip this step.
88 -
89 -If you are upgrading to 0.9.3 or greater, you should make the images/
90 -directory and subdirectories writable by the web server.
91 -
92 -Prepare your branches if you are running any off of your hub site. Depending
93 -on the owner of these directories will affect the commands to run. The base
94 -directory of each branch will need to be writable.
95 -
96 -If the owner is the webserver and you have root access:
97 -chmod o+rwx branch1/
98 -chmod o+rwx branch2/
99 -etc...
100 -
101 -otherwise:
102 -chmod 0777 branch1/
103 -chmod 0777 branch2/
104 -etc...
105 -
106 -The images and themes directories will also need to be writable for the
107 -upgrade:
108 -
109 -chmod -R o+rwx branch1/{images,themes}
110 -chmod -R o+rwx branch2/{images,themes}
111 -
112 --or-
113 -
114 -chmod -R 0777 branch1/{images,themes}
115 -chmod -R 0777 branch2/{images,themes}
116 -
117 -If the webserver is not given the proper permissions then the branch upgrade
118 -will not be successfull.
119 -
120 -
121 -Once you have you have finished these steps (and ONLY after) should you
122 -continue.
123 -
124 -Running the Upgrade
125 ---------------------------------------
126 -Now you can untar the new files into your installation. If you go to
127 -your site's index.php file, you will see a few error messages. The
128 -aforementioned index.php prevents most people from seeing these messages.
129 -Point your browser to 'http://www.myWebSitesName.com/setup/' where
130 -'www.myWebSitesName.com' is the address for your web site.
131 -
132 -The first thing the upgrader will do is upgrade your core modules. It
133 -will also check to see if you are running any branch sites and automatically
134 -upgrade them as well.
135 -
136 -You should receive a 'Core Updated!' message. Underneath these messages
137 -will be a list of modules that appear to need upgrading as well. Click
138 -the checkboxes of the modules you want updated (or click the 'Check All' button
139 -to check all of them) and click the 'Update Modules' button. Your site and
140 -all your branch sites should now be updated.
141 -
142 -If you made a warning index.php file, dump it and put the real file back.
143 -You should now be able to use your site as normal.
144 -
145 -Should something go wrong
146 ---------------------------------------
147 -If you go to your site and receive errors the FIRST thing you should try
148 -is closing your browser, reopening it, and trying to use your site again.
149 -Sometimes old sessions will conflict with the upgraded information.
150 -
151 -If you get an error message or your sites still don't function, restore your
152 -backed up databases and files and try again. If it STILL doesn't work, contact
153 -us via Sourceforge, we want to know what went wrong.
154 -
155 -Please include your OS, web server, PHP, and phpWebSite version information.
156 -Also include any error messages that were displayed. The more data you supply
157 -us, the better chance you will receive help.
158 -
159 -You may also try using the repair.php file. It contains answers to a few
160 -commonly experienced problems.
161 -
162 -Returning to update.php
163 ----------------------------------------
164 -Most of the time, Boost will handle your upgrade needs. However, should
165 -an upgraded module cause problems before you can get to the Boost module,
166 -you can always return to update.php to upgrade the offending module.
167 -
168 -Securing your Site
169 ----------------------------------------
170 -Although setup.php, update.php, and repair.php require passwords to enter,
171 -you may want to prevent malicious users (read: jerks) from even accessing
172 -these files. One way would be to limit read access on that directory after
173 -you are finished using it. Another measure would be to alter your
174 -allow_setup.php file. Open this file in an editor and change the 'TRUE'
175 -to 'FALSE' like so:
176 -
177 -$_SESSION['allow_setup'] = FALSE;
178 -
179 -Change this back to TRUE when you need to update again.
180
181 diff --git a/www-apps/phpwebsite/metadata.xml b/www-apps/phpwebsite/metadata.xml
182 deleted file mode 100644
183 index cce709fb534..00000000000
184 --- a/www-apps/phpwebsite/metadata.xml
185 +++ /dev/null
186 @@ -1,12 +0,0 @@
187 -<?xml version="1.0" encoding="UTF-8"?>
188 -<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
189 -<pkgmetadata>
190 - <maintainer type="project">
191 - <email>web-apps@g.o</email>
192 - <name>Gentoo Webapps</name>
193 - </maintainer>
194 - <longdescription>phpWebSite provides a complete web site content management system. Web-based administration allows for easy maintenance of interactive, community-driven web sites.</longdescription>
195 - <upstream>
196 - <remote-id type="sourceforge">phpwebsite</remote-id>
197 - </upstream>
198 -</pkgmetadata>
199
200 diff --git a/www-apps/phpwebsite/phpwebsite-1.7.2.ebuild b/www-apps/phpwebsite/phpwebsite-1.7.2.ebuild
201 deleted file mode 100644
202 index e2b172dd995..00000000000
203 --- a/www-apps/phpwebsite/phpwebsite-1.7.2.ebuild
204 +++ /dev/null
205 @@ -1,43 +0,0 @@
206 -# Copyright 1999-2012 Gentoo Foundation
207 -# Distributed under the terms of the GNU General Public License v2
208 -
209 -EAPI=4
210 -
211 -inherit webapp
212 -
213 -MY_PV=${PV//./_}
214 -DESCRIPTION="phpWebSite Content Management System"
215 -HOMEPAGE="http://phpwebsite.appstate.edu"
216 -SRC_URI="mirror://sourceforge/${PN}/${PN}_${MY_PV}.tar.gz"
217 -
218 -LICENSE="LGPL-2.1"
219 -KEYWORDS="~amd64 ppc ~ppc64 x86"
220 -IUSE="+mysql postgres"
221 -REQUIRED_USE="|| ( mysql postgres )"
222 -
223 -S="${WORKDIR}"/${PN}_${MY_PV}
224 -
225 -RDEPEND="virtual/httpd-php
226 - dev-lang/php[gd,mysql?,postgres?]"
227 -
228 -src_install() {
229 - webapp_src_preinst
230 -
231 - dodoc README docs/*
232 -
233 - cp -r * "${D}/${MY_HTDOCSDIR}"
234 -
235 - # Files that need to be owned by webserver
236 - webapp_serverowned ${MY_HTDOCSDIR}/config
237 - webapp_serverowned ${MY_HTDOCSDIR}/config/core
238 - webapp_serverowned ${MY_HTDOCSDIR}/files
239 - webapp_serverowned ${MY_HTDOCSDIR}/images
240 - webapp_serverowned ${MY_HTDOCSDIR}/mod
241 - webapp_serverowned ${MY_HTDOCSDIR}/logs
242 - webapp_serverowned ${MY_HTDOCSDIR}/templates
243 - webapp_serverowned ${MY_HTDOCSDIR}/javascript
244 -
245 -# webapp_postinst_txt en ${FILESDIR}/postinstall-en.txt
246 -
247 - webapp_src_install
248 -}