Bug 356291 - phpMyAdmin 2.11.2 is released
Summary: phpMyAdmin 2.11.2 is released
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: phpMyAdmin
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Mike McGrath
QA Contact: Fedora Extras Quality Assurance
URL: http://www.phpmyadmin.net/home_page/d...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-29 10:23 UTC by Robert Scheck
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version: 2.11.2.2-1.fc8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-22 03:34:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2007-10-29 10:23:19 UTC
Description of problem:
PhpMyAdmin 2.11.2 was released on September 27th, 2007 and Fedora Development 
hangs still around the older 2.11.0 / 2.11.1.2 (depends whether you look to CVS 
or to the repository).

Version-Release number of selected component (if applicable):
phpMyAdmin-2.11.0-1
phpMyAdmin-2.11.1.2

Expected results:
phpMyAdmin-2.11.2-1 or newer ;-)

Additional info:
A simple version bump did the trick for me.

Comment 1 Mike McGrath 2007-10-29 13:12:16 UTC
Already ready -
https://admin.fedoraproject.org/updates/F7/pending/phpMyAdmin-2.11.1.2-1.fc7

Just waiting on releng.

*** This bug has been marked as a duplicate of 237882 ***

Comment 2 Robert Scheck 2007-10-29 13:20:37 UTC
Ehm: 2.11.1.2 is not the same as 2.11.2 - watch out!

Comment 3 Mike McGrath 2007-10-29 13:34:06 UTC
They snuck one in on me :)  I'll get that built and out today.

Comment 4 Fedora Update System 2007-11-22 03:34:20 UTC
phpMyAdmin-2.11.2.2-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2007-11-22 03:37:28 UTC
phpMyAdmin-2.11.2.2-1.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.