I had no problems upgrading to rc3 today, but I notice after quite some hours and multiple cron runs, updatedb etc, the Hosting module is detecting my rc3 version but still is recommending rc2 (via Update Status module, and a drush update)

web@li35-166:/opt/www/deploy/drupal-6.13/sites$ drush update
Refreshing update status information ...
Done.
Update information last refreshed: Sat, 08/15/2009 - 18:53
 Name                 Installed version  Proposed version  Status           
<snip irrelevancies>
 Hosting              6.x-0.3-rc3        6.x-0.3-rc2       Update available

Otherwise, no problems!

Comments

Anonymous’s picture

Anonymous (not verified) commented

Drush dl also grabs the rc2 version, git.koumbit.net still seems unaware of rc3 since it came out on the weekend, so I think we have a tagging issue here

web@li35-166:~$ drush dl hostmaster
Project hostmaster (6.x-0.3-rc2) downloaded to /home/web/.                                                                                        [success]
web@li35-166:~$ drush dl hosting
Project hosting (6.x-0.3-rc2) downloaded to /home/web/.                                                                                           [success]
web@li35-166:~$ drush dl provision
Project provision (6.x-0.3-rc2) downloaded to /home/web/.
Anonymous’s picture

Anonymous (not verified) commented
Priority: Minor » Critical

marking as critical since if anyone follows the (out of date) instructions in hostmaster INSTALL.txt, they'll drush dl rc2 versions.

See also 550352 regarding INSTALL.txt and documentation fixups needed

anarcat’s picture

anarcat commented

So let's hope this gets fixed when we eventually release an RC4 (as it's obvious it will be necessary).

Anonymous’s picture

Anonymous (not verified) commented

I don't know if you did something earlier after our chat. It has literally *just* started to work now. I didn't make it up, honest! :/

Oh well, thanks whoever fixed it.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed
anarcat’s picture

anarcat commented
Status: Fixed » Needs work

I didn't do anything. Maybe you tested this too early in the release cycle and it takes a while for the update_status stuff to get updated (it's a separate XML stream). So in that case, maybe we need to update the INSTALL.txt to take that into account: in fact, I feel like the way INSTALL.txt is right now (ie. downloading provision, hosting and other with drush) actually breaks its intended purpose (of being in sync with HEAD). Maybe we should tell drush to download using CVS?

Not sure how to best fix this.

Anonymous’s picture

Anonymous (not verified) commented

Maybe you tested this too early in the release cycle and it takes a while for the update_status stuff to get updated

5 days?!

That said, I never heard anyone reproduce this.. who knows.. maybe it was only occuring on my Linode (byt he time I saw it was 'fixed', this was on separate infrastructure).

anarcat’s picture

anarcat commented
Status: Needs work » Postponed (maintainer needs more info)

So I just released RC4. Tell me if the problem is still there. Anyways, the INSTALL.txt improvements mitigate much of the problems raised here. Besides, this is a drupal.org issue and not really hosting (i think).

Still, please test again.

jonhattan’s picture

jonhattan
Primary language Spanish
Location Plasencia
commented
Status: Postponed (maintainer needs more info) » Needs review

It seems right here:

Update information last refreshed: Fri, 08/21/2009 - 09:06

Update status information on all installed and enabled Drupal modules:
 Name                 Installed version  Proposed version  Status           
 Hosting              6.x-0.3-rc3        6.x-0.3-rc4       Update available 
 Eldir                6.x-0.3-rc3        6.x-0.3-rc4       Update available
Anonymous’s picture

Anonymous (not verified) commented
Status: Needs review » Fixed

Confirmed, installing a freshy with rc4, using only drush commands for the aegir components, rc4 is being downloaded. I think we can consider this closed, whatever you did during the rc4 release is the way to do it :)

hhg’s picture

hhg commented

5 days?!

That said, I never heard anyone reproduce this.. who knows.. maybe it was only occuring on my Linode (byt he time I saw it was 'fixed', this was on separate infrastructure).

I saw the same problem, drush would only download rc2 for several days. And now it works, rc4 is suggested. Also on a Linode, but I don't think that matters.

Anonymous’s picture

Anonymous (not verified) commented

Good to hear it wasn't just me :) thanks for the feedback.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

theohawse’s picture

theohawse commented

Okay, now I'm still having issues, just update to rc4 from rc2 but update status still says rc2 is installed.

Here's what I ran:

OLD_AEGIR_DIR=/var/aegir/hostmaster-6.x-2.0-rc2
AEGIR_VERSION=6.x-2.0-rc4
AEGIR_DOMAIN=aegir.rockdiamond.net

cd $OLD_AEGIR_DIR
drush hostmaster-migrate $AEGIR_DOMAIN $HOME/hostmaster-$AEGIR_VERSION

What did I miss?

theohawse’s picture

theohawse commented
Version: 6.x-0.3-rc3 » 6.x-0.3-rc4
Priority: Critical » Normal

Changed to rc4 since rc3 vs rc4 is just a packaging hiccup.