What is the rationale behind phpMyAdmin 2.7.0 as a CentOS package? The new 2.8.0.2 introduces a new authentication mechanism. How do you plan to handle upgrades ie if someone has 2.7.0 and needs to get 2.8?
I know Gentoo and Debian have phpbb (which I'm not concerned about) but they must face similar problems with all the security releases.
Improve the mailing list by performing a simple search before posting and reading the faq/etiquette. Thank you!!
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Mon, Apr 03, 2006 at 11:11:03AM -0700, Mike Stankovic enlightened us:
What is the rationale behind phpMyAdmin 2.7.0 as a CentOS package? The new 2.8.0.2 introduces a new authentication mechanism. How do you plan to handle upgrades ie if someone has 2.7.0 and needs to get 2.8?
I know Gentoo and Debian have phpbb (which I'm not concerned about) but they must face similar problems with all the security releases.
Improve the mailing list by performing a simple search before posting and reading the faq/etiquette. Thank you!!
I think these reasons are why the phpMyAdmin package will probably go away. There are too many upgrade issues to keep up with to make it worth packaging.
Matt
I think these reasons are why the phpMyAdmin package will probably go away. There are too many upgrade issues to keep up with to make it worth packaging.
Correct. This package was requested and produced, however there has been very little feedback about it. The phpMyAdmin folks seem to change things very rapidly and I do not feel overly comfortable with a package that changes this often being moved to centosplus. The dev.centos.org repo is meant to be a testing grounds before packages move to centosplus or Extras, and as such, if phpmyadmin isn't going to make the leap, there's no need to maintain it in dev. Unless people provide feedback about the package, or show some overwhelmingly stellar reason why it should continue to exist, I'll probably remove it soon.
-- Any sufficiently advanced technology is indistinguishable from magic. -Arthur C. Clarke
Mike Stankovic wrote:
What is the rationale behind phpMyAdmin 2.7.0 as a CentOS package? The new 2.8.0.2 introduces a new authentication mechanism. How do you plan to handle upgrades ie if someone has 2.7.0 and needs to get 2.8?
You might have a look at this package here: http://remi.collet.free.fr/rpms/SRPMS/phpMyAdmin-2.8.0.2-1.fc4.remi.src.rpm
or maybe this one submitted to Fedora Extras: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187843 ...probably best to try this one and give feedback on the bug report.
Greg
Greg Swallow - SkyNet wrote:
Mike Stankovic wrote:
What is the rationale behind phpMyAdmin 2.7.0 as a CentOS package? The new 2.8.0.2 introduces a new authentication mechanism. How do you plan to handle upgrades ie if someone has 2.7.0 and needs to get 2.8?
You might have a look at this package here: http://remi.collet.free.fr/rpms/SRPMS/phpMyAdmin-2.8.0.2-1.fc4.remi.src.rpm
or maybe this one submitted to Fedora Extras: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187843 ...probably best to try this one and give feedback on the bug report.
hi Greg,
do these pkgs maintain upgrade path from 2.7.x series installs via rpm ?
Karanbir Singh wrote:
hi Greg,
do these pkgs maintain upgrade path from 2.7.x series installs via rpm ?
I don't know. I didn't use the phpmyadmin rpm from dev.centos.org, and I didn't check if the config.inc.php file from my old 2.6 or 2.7 install worked on 2.8, but I assume it would. It looks like both rpms will create a new config.inc.php file though when installed. I used the one from Remi Collet, but ended up changing the authorization method and protecting the directory with mod_auth_external. I'm happy to see someone pushing it in Fedora Extras though - looks like that was just posted today.
Greg
do these pkgs maintain upgrade path from 2.7.x series installs via rpm ?
I don't know. I didn't use the phpmyadmin rpm from dev.centos.org, and I didn't check if the config.inc.php file from my old 2.6 or 2.7 install worked on 2.8, but I assume it would. It looks like both rpms will create a new config.inc.php file though when installed. I used the one from Remi Collet, but ended up changing the authorization method and protecting the directory with mod_auth_external. I'm happy to see someone pushing it in Fedora Extras though - looks like that was just posted today.
I took a look at Remi Collet's package. He's got some interesting scripts in the spec file. They attempt to set up the pma_* db and tables for you in mysql. I'm not sure I like the idea of an rpm install/upgrade operating directly on a (production) database. It might very well be harmless, but it just doesn't give me warm fuzzy feelings.
-- Any sufficiently advanced technology is indistinguishable from magic. -Arthur C. Clarke
On Tuesday 04 April 2006 07:22, Jim Perrin wrote:
do these pkgs maintain upgrade path from 2.7.x series installs via rpm
I don't know.
I'm not sure I like the idea of an rpm install/upgrade operating directly on a (production) database.
For what it's worth, the PostgreSQL 8.1 RPMs will not upgrade a previous RPM based install, either. You would have found the way previous PostgreSQL RPMs attempted to do upgrades less than warm and fuzzy, too. I know I didn't find them to be warm and fuzzy (and I wrote the procedure!).
Jim Perrin wrote:
I took a look at Remi Collet's package. He's got some interesting scripts in the spec file. They attempt to set up the pma_* db and tables for you in mysql. I'm not sure I like the idea of an rpm install/upgrade operating directly on a (production) database. It might very well be harmless, but it just doesn't give me warm fuzzy feelings.
Yes, it's not an rpm that you could include on a CD install, that's for sure. I think the Fedora Extras rpm will be, I haven't really looked at it yet though.
Those scripts aren't even necessary if you use auth_type = CONFIG, as I have always used.
From the docs:
For 'HTTP' and 'cookie' modes, phpMyAdmin needs a controluser that has only the SELECT privilege on the mysql.user (all columns except "Password"), mysql.db (all columns), mysql.host (all columns) and mysql.tables_priv (all columns except "Grantor" & "Timestamp") tables. You must specify the details for the controluser in the config.inc.php file under the $cfg['Servers'][$i]['controluser']& $cfg['Servers'][$i]['controlpass'] settings.
Greg
-
Greg Swallow - SkyNet -
Jim Perrin -
Karanbir Singh -
Lamar Owen -
Matt Hyclak -
Mike Stankovic