On Monday, October 26, 2015 08:56:08 PM Mick wrote: > On Monday 26 Oct 2015 20:38:18 Dan Johansson wrote: > > The other day I noticed that the behavior of webapp-config has changed. > > I have USE=vhost enabled and I have a directory structure where each > > "app" is installed in htdocs in its own v-host like this: > > > > /var/www/app-1.int.dmj.nu/htdocs/ > > /var/www/app-2.int.dmj.nu/htdocs/ > > > > Before I could simply do the following to upgrade an app > > # webapp-config -h app-1.int.dmj.nu -U app-1 1.2.3 > > > > And this would update the app-1 in /var/www/app-1.int.dmj.nu to version > > 1.2.3 > > (note, there is NO -d for directory in there) > > > > Doing this now results in this: > > * Install dir flag not supplied, defaulting to "app-1". > > * Fatal error: Cannot clean! > > * Fatal error: No package installed in > > /var/www/app-1.int.dmj.nu/htdocs/app-1 > > * Fatal error(s) - aborting > > Did you try to run it like so: > > webapp-config -h app-1.int.dmj.nu -U . 1.2.3 > > or even better: > > webapp-config -U -h app-1.int.dmj.nu 1.2.3 > > The above error you're getting above points to your call for 'app-1' cause > webapp to assume the directory is '/var/www/app-1.int.dmj.nu/htdocs/app-1'
Had the same issue myself. In the past, I had to specify the application name (app-1) when doing an upgrade. I take it that isn't necessary anymore? Will test that. -- Joost
signature.asc
Description: This is a digitally signed message part.
