Upgrading Drupal

Hey, this is cross-posted from http://drupal.org/node/64662 because I was hoping someone in the forum might be able to help me.

I upgraded my Drupal installtion from 4.6.6 to 4.7.0, and upgraded to the CVS version of aggregator2. However, all the nodes which were created with aggregator2 in the past seem to have lost their authors, and the system doesn't seem to have matched up the old nodes with aggregator2 (you can't edit the content or anything because I guess the nodes don't know what module they belong to?). Is there any way to fis this? I'd prefer if I didn't have to go through and manually edit/fix each post I aggregated before the upgrade...
Updates
#1 submitted by canadrian@elect... on May 20, 2006 - 12:00

Fixed compatability of old nodes with new version of the module by reading the CVS logs. Apparently I had to run the following SQL:

UPDATE node SET type = 'aggregator2_feed' WHERE type = 'aggregator2-feed';
UPDATE node SET type = 'aggregator2_item' WHERE type = 'aggregator2-item';

That sorted out the node associations. But for some reason all the aggregator2 feed items still have no authors. Any ideas? Is there more SQL I need to run?
#2 submitted by canadrian@elect... on May 20, 2006 - 12:05
Title: Old aggregator2 nodes not compatible? » New nodes have no author either

A cron run just completed, and aggregator2 syndicated some more content. However, the new feed items have no author either. I have checked the settings, and the author field is set...

Plz Tell Me
what step i follow to Create new revision
and how is see the created revision.

Thanks

An unrecoverable error has occured. You can find the error message below. It is advised to copy it to the clipboard for reference. Please continue to the update summary
An HTTP error 404 occured. update.php?op=do_update

The update process was aborted prematurely while running update #129 in system.module. All other errors have been logged. You may need to check the watchdog database table manually.

:-( I can never get through an upgrade without problems...

Drupaling Folks,

I upgraded my 4.6.6 installation successfully to 4.7 rc3 and save
for my 'og' module, all went well. During the og bit of the update,
a number of mySQL DB errors were logged on the update screen.

Here's the online summary of those

Duplicate column name 'website' query: ALTER
Can't DROP 'PRIMARY'; check that
Duplicate column name 'is_admin' query: ALTER ...
Duplicate column name 'is_active' query: ...
Duplicate column name 'og_role' query: ALTER ...

As per the latest instructions, I had setup the og module folder
with the og 4.7 version code with the og.install file as well. So
I think the update attempted to upgrade the DB to og 4.7 and
failed. For the timebeing I had disabled og to work on other stuff.

I'd like to get og to work again, and it looks the update left the DB
in some inconsistent state. When I enable og in the settings
(in 4.7.rc3 upgraded status) after enabling the module, I start seeing
big red SQL warning messages.

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') AND ISNULL(na.gid)' at line 1 query: SELECT n.nid FROM node n LEFT JOIN node_access na ON n.nid = na.nid AND realm LIKE '%og%' WHERE n.type NOT IN () AND ISNULL(na.gid) in /path/to/site/includes/database.mysql.inc on line 120.

I know this is a rather basic question, but I can't seem to find the answer anywhere.

I have a 4.7 installation and am installing some contrib modules. I am running into problems with a few and see that there are bugs statused "patch (ready to be committed)" against version 4.7. I assume this means that it is safe to apply these patches without waiting for the modules to be formally updated and released.

I'm using the /drupal/databse/updates.inc revision 1230 and I get those warnings: