I'm marking this as a support request, as I haven't yet seen anyone else complain of not being able to install aegir 1.4 via the .debs, and I have an odd setup.
I'm working on automating installs of Aegir into VirtualBox machine via Vagrant & Puppet. Manual apt-get installs had been working until recently (I believe the 1.4 .deb release). With 'env DPKG_DEBUG apt-get install aegir', I now get the following:
Setting up aegir-hostmaster (1.4+13.gbcf2cfe-1+1.gcf67491) ...
installing the Aegir frontend (Drupal with the hostmaster profile), please wait...
Unable to download drush_make-6.x-2.3.tar.gz to [error]
/tmp/drush_tmp_1318536414 from
http://ftp.drupal.org/files/projects/drush_make-6.x-2.3.tar.gz
The drush command 'make [error]
/usr/share/drush/commands/provision/aegir.make
/var/aegir/hostmaster-6.x-1.x' could not be found.
A Drupal installation directory could not be found [error]
Could not download platform using drush make. No platform present [error]
Aegir 6.x-1.x automated install script
==============================================================================
The aegir user can write to /tmp. 'drush dl drush_make' results in:
No release history available for drush_make 7.x.
So specifying a version, 'drush dl drush_make-6.x-2.3' results in:
Destination directory /usr/share/drush/commands is not writable. [error]
Project drush_make (6.x-2.3) could not be downloaded to /usr/share/drush/commands/drush_make. [error]
When #1214216: Drush should prefer per-user directory to global directory when later is not writable gets in, that won't be an issue any more, but in the mean time I made /usr/share/drush/commands/ world-writeable. After all that, I got exactly the same errors, most notably
Unable to download drush_make-6.x-2.3.tar.gz to /tmp/drush_tmp_1318536414 from
http://ftp.drupal.org/files/projects/drush_make-6.x-2.3.tar.gz
But the aegir user *can* wget that file to that location... curl wasn't installed though, so I'm checking that out next.
Comments
Comment #1
anarcat CreditAttribution: anarcat commentedwe're having the same issue in jenkins, btw, no idea wtf is going on... maybe something wrong on d.o?
Comment #2
ergonlogicThis is just weird:
Why would drush dl fail from a home/ directory, but succeed from somewhere like /tmp?
Comment #3
omega8cc CreditAttribution: omega8cc commentedSee #1270724: Drush should not require write permissions on site directory.
You need this patch: http://drupal.org/node/1263124#comment-4957340
Comment #4
omega8cc CreditAttribution: omega8cc commentedOr this one: http://drupal.org/node/1272820#comment-5113976 however I have tested and I'm using only that quick hack from #3 above.
Comment #5
ergonlogicThanks omega8cc!
The patch from #3 worked like a charm. Perhaps not the "right way", but still... How do we get such a fix into Aegir? Do we need a Drush 4.6 release, or can we apply that patch (or one like it) in the Debian package?
Comment #6
anarcat CreditAttribution: anarcat commentedI don't think patching drush in the aegir package is wise, and i will not hijack the drush release process in the debian package, too much trouble.
the proper fix for this is to package drush make (#980152: package drush_make for Debian).
anyways, we have a workaround - just start the installer in a location you can write to! :)
Comment #7
ergonlogicYeah, I tried that, but it didn't work for the aegir installation, just for 'drush dl'.
Comment #8
Steven Jones CreditAttribution: Steven Jones commentedSo for now, I've popped a little fix into our debian package, that does what anarcat suggests, runs the installer from a location our aegir user can write to.
http://drupalcode.org/project/provision.git/commitdiff/b8bdaee47745ad0ce...
Comment #9
Steven Jones CreditAttribution: Steven Jones commentedSeems like we did the proper fix in #6 then.