[TYPO3-english] Fatal error on upgrading from 6.1.7 to 6.2.0beta5
Sergio Catalá
scatala.enet at gmail.com
Fri Feb 21 14:34:30 CET 2014
Sorry Markus and Thomas to create such a discussion about the issue.
I already tried yesterday to get the master branch on GIT and point my
symlink to it, but this didn't solve the problem. Another exception is
shown:
Fatal error: Uncaught exception
'TYPO3\Flow\Package\Exception\CorruptPackageException' with message 'The
package "050_coretypo3_src-6.2-devtypo3sysextabout" does not contain a
valid package class. Check if the file
"/var/www/server/vhosts/host/htdocs/typo3conf/ext/050_core/typo3_src-6.2-dev/typo3/sysext/about/Classes/Package.php"
really contains a class called
"050_coretypo3_src-6\2-devtypo3sysextabout\Package".' in
/var/www/server/vhosts/host/htdocs/typo3conf/trunk/050_core/typo3_src-6.2-dev/typo3/sysext/core/Classes/Package/PackageFactory.php
on line 61
Is there an opened issue for this on forge, Markus? Should I inform
about the bug?
I tried yesterday a clean upgrade from 4.7 to 6.0, later from 6.0 to
6.1, and later from 6.1 to 6.2, to check if this solved the problem. But
without success.
Regards,
Sergio
On 21/02/14 13:28, Markus Klein wrote:
> Hi Thomas,
>
> sorry, but
>> I've never seen a TYPO3 version since 4.2 with so many breaking changes and it's hard to imagine that we'll get a 'smooth migration' for the vast majority of 4.5 sites. Hopefully they'll postpone the release again, since there might be too many bleeding edges for production use.
> yes, this is ranting for me. And that frustrates myself.
>
> I of course appreciate it, if you try to help users, but sentences like the ones above, shed a false light, IMHO, on the current state of 6.2.
> What "so many breaking changes" are you referring to?
>
> I fully understand your frustration, and I also spent quite some hours on bugfixing and reviewing and sometimes it is really breathtaking how long it takes to get this and that fixed. But that is open source, everybody has the right to comment on things, or simply to do nothing.
>
> Regarding your firm understanding of GIT. It does not require to understand the whole GIT tool to test patches. Actually you're done with 3 commands.
> (btw: not many people fully understand the whole GIT, or even the mechanics which is behind it, that is just f*** complex)
>
> So, you're welcome to approach me, if you need tips on the tools and on the reviewing process. And it would be great if you could test your upgrade paths from 1.5 months ago again on current master. Maybe even apply the change sets I posted. Then things should run pretty smooth.
>
> Kind regards
> Markus
>
> ------------------------------------------------------------
> Markus Klein
> TYPO3 CMS Active Contributors Team Member
>
>> Hi Markus,
>>
>> so this is 'ranting' for you if I'm trying to help other users? Telling him 'yes,
>> there might me issues using a dev-version', but there might also be ways to
>> cure them?
>>
>> Spent hundreds of hours fixing things the last month, and I'm currently losing
>> my patience. Would love to review changes, but I can't, since I just don't
>> know how. I'm still new to Git and I never use tools until I have a firm
>> understanding.
>>
>> Thanks again for hauling me to the next level of demotivation.
>>
>> Regards,
>>
>> Thomas
>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
More information about the TYPO3-english
mailing list