This update has a lot of files :
SRPMS
kdevplatform4-1.7.3-1.mga5
kdevelop4-4.7.3-1.mga5
kdevelop4-php-1.7.3-1.mga5
kdevelop4-php-docs-1.7.3-1.mga5


RPMS
lib64kdevplatformdocumentation8-1.7.3-1.mga5.x86_64 lib64kdevplatformjsontests8-1.7.3-1.mga5.x86_64
lib64kdevplatform4-devel-1.7.3-1.mga5.x86_64
kdevplatform4-1.7.3-1.mga5.x86_64
lib64kdevplatformutil8-1.7.3-1.mga5.x86_64 lib64kdevplatformshell8-1.7.3-1.mga5.x86_64 lib64kdevplatformproject8-1.7.3-1.mga5.x86_64 lib64kdevplatformlanguage8-1.7.3-1.mga5.x86_64 lib64kdevplatformvcs8-1.7.3-1.mga5.x86_64
lib64sublime8-1.7.3-1.mga5.x86_64
lib64kdevplatformdebugger8-1.7.3-1.mga5.x86_64 lib64kdevplatforminterfaces8-1.7.3-1.mga5.x86_64 lib64kdevplatformtests8-1.7.3-1.mga5.x86_64 lib64kdevplatformoutputview8-1.7.3-1.mga5.x86_64

kdevelop4-4.7.3-1.mga5.x86_64
plasma-dataengine-kdevelopsessions-4.7.3-1.mga5.x86_64
plasma-applet-kdevelopsessions-4.7.3-1.mga5.noarch
kdevelop4-devel-4.7.3-1.mga5.x86_64

kdevelop4-php-1.7.3-1.mga5.x86_64

kdevelop4-php-docs-1.7.3-1.mga5.x86_86

Status: NEW => ASSIGNED

I have also rebuilt 

kdevelop4-xdebug-1.5.60-2.mga5
kdevelop4-executebrowser-1.5.60-2.mga5

so they are to be installed too.

Tested procedure :

1 "urpmi kdevelop4-php-docs kdevelop4-xdebug kdevelop4-executebrowser"
2 Launch kdevelop, ensure that xdebug and execute browser appear in configuration>plugins>other
3 Open a project, but as this is a dev tool, I feel it does not need much testing from QA.

I will use it myself for a few days, then report here.

Whiteboard: (none) => has_procedure

mga5  x86_64  KDE4

Ensured that all the needed packages were installed then updated the *4.7.1 and *1.7.1 packages to *4.7.3 and *1.7.3.
Launched Kdevelop from the menu
Settings -> Configure KDevelop -> Plugins
'Other' panel listed:
Execute Browser
Execute Scripts
Plasmoid Launcher
XDebug Support

All were checked.

Create new project
From General selected Qt -> Test
Name kdevelop_qt_0 in ~/projects
No version control

Finished up.
Editing panel for kdevelop_qt_0.cpp appeared.
Wrote a couple of dummy lines:
// Nothing here folks.  Move along.
exit( 0 );
and saved it.  This raised an error concerning a 'src' directory.
The cpp file had been saved already to ~/projects/kdevelop_qt_0
[lcl@vega kdevelop_qt_0]$ ls
CMakeLists.txt     kdevelop_qt_0.h      main.cpp
kdevelop_qt_0.cpp  kdevelop_qt_0.kdev4  tests
However, I created the src directory and tried saving again and a copy of the file appeared in src.
Closed down and restarted kdevelop and it opened at the project page, displaying the last code.
That is as far as I can go so over to you José.  If your report is positive I shall OK the update.

CC: (none) => tarazed25

All is Ok here : php project debugging with xdebug, integrated help.

Whiteboard: has_procedure => has_procedure MGA5-64-OK MGA5-32-OK

Thanks.  All it needs now is an advisory.

Validating. Used comment 0 as the advisory.

Please push to 5 updates, thanks.

Whiteboard: has_procedure MGA5-64-OK MGA5-32-OK => has_procedure advisory MGA5-64-OK MGA5-32-OK
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0024.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Two SRPMS were missing from the files list:
kdevelop4-executebrowser-1.5.60-2.mga5.src.rpm
kdevelop4-xdebug-1.5.60-2.mga5.src.rpm

SVN logs say they were rebuilt against the kdevelop4 4.7.3 update.

José, were those rebuilds needed?  If so, we'll need to add them to the advisory file and get them pushed.  If not, we should ask the sysadmins to remove them from updates_testing.

Resolution: FIXED => (none)
Status: RESOLVED => REOPENED

(In reply to David Walser from comment #8)
> Two SRPMS were missing from the files list:
> kdevelop4-executebrowser-1.5.60-2.mga5.src.rpm
> kdevelop4-xdebug-1.5.60-2.mga5.src.rpm
> 
> SVN logs say they were rebuilt against the kdevelop4 4.7.3 update.
> 
> José, were those rebuilds needed?  If so, we'll need to add them to the
> advisory file and get them pushed.  If not, we should ask the sysadmins to
> remove them from updates_testing.

Yes they are needed, please push them.

Thanks.  Missing SRPMS added to the advisory in SVN.  Sysadmins, please push them.

Does the ID line have to be removed from the advisory in svn for the push to work?

CC: (none) => davidwhodgins

I don't know.  How would it know then to re-use the same ID from before?  I don't know who did it, but someone recently go this to work for the spamassassin/perl-Net-DNS update.  Hopefully they'll get to this one soon too!

I believe added srpms need to be pushed manually - sysadmins please.
comment 8

missing (s)rpms pushed.

advisories.mageia.org is already listing the srpms just pushed

Status: REOPENED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED