Upgrade Beta5 to RC1 PHP errors

Had similar issues;

    * warning: include_once(./sites/all/modules/rules/rules/rules.rules_defaults.inc) [function.include-once]: failed to open stream: No such file or directory in C:\xampp\htdocs\drupal6\sites\all\modules\rules\rules\rules.module on line 946.

    * warning: include_once() [function.include]: Failed opening './sites/all/modules/rules/rules/rules.rules_defaults.inc' for inclusion (include_path='.;C:\xampp\php\pear\') in C:\xampp\htdocs\drupal6\sites\all\modules\rules\rules\rules.module on line 946.

Not sure why pear is mentioned, is this something to do with the module? I don't recall ever setting a path like this :(

sorry, forgot to bump this to critical.

Also noticed it says;

The following queries were executed
rules module
Update #6004

    * No queries

Is this correct?

Thanks :)

@#2: Yep, that's correct.

This just a caching problem. Try loading the page "admin/build/modules" once, this should fix it. I fixed the update in the -dev version to also do the missing cache clearing.

I've also added this to the described update procedure in the release notes - please report if it's working for you.

Found this thread through #444232: Errors after updating to rc1 and running update.php

Just updated from 6.x-1.0-beta5 to 6.x-1.1 and got the same set of errors, so I think there's still something wrong in some section of the upgrade path...?

warning: include_once(./sites/mysite/modules/rules/rules/rules.rules_defaults.inc) [function.include-once]: failed to open stream: No such file or directory in /home/sites/org/biocomp/drupal/modules/rules/rules/rules.module on line 955.

warning: include_once() [function.include]: Failed opening './sites/mysite/modules/rules/rules/rules.rules_defaults.inc' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /home/sites/org/biocomp/drupal/modules/rules/rules/rules.module on line 955.

I'm just going to ignore it, since no one seemed to think it was a big deal, but just thought I'd share :)

Thank you for sharing and confirming it still occurs. No need to reopen though, the fix is in the docs.

Updated component.