TYPO3 Core

Hi,

we discovered the following issue:

When uploading a new version of an extension directly in EM, the wrong dependency checks are made. Not for the new (uploaded) version, but for the previous one which is to be replaced. So a direct update of the extension is not possible, it has to be removed first and then the new version uploaded. Including all extensions with dependencies.

Detailed explanation:
A website with TYPO3 4.5.x has to me upgraded to 6.2.12.
Website uses DAM, includes some extension which use AND REQUIRE the DAM extension. Dependencies have bee nset in ext_emconf.php.
During the upgrade DAM has bee nremoved, all data migrated.
Also the extensions have been rewritten to use FAL instead of DAM. Extensions work fine on development, now the old extension versions have to be replaced in the test system. But directly replacing the old version by uloading the new one fails. EM returns "The package "<ext_key>" depends on "dam" which is not present in the system." We have checked the ext_emconf.php in the archive being uploaded: all dependencies in the new versions have been removed, string "dam" cannot be found in the file.
The only explanation for this issue is that EM checks the dependencies for the previous version of the extension, but not for the newly uploaded one.
Even deactivation of the extension and deleting it from the filesystem wasn't enough. We also had to remove its entry in typo3conf/PackageStates.php to get it uploaded and installed again. But if you have some other extensions depending on the current one (and we have here, DAM or FAL doesn't matter here), this leads to a larger number of extenisons which have to be removed first and then activated again, only because of this bug. Very annoying...