-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install Errors #98
Comments
Same problem here, on an up-to-date 64 bits Debian Jessie, with backports repository enabled:
|
This bug was fixed on git by issue #90, but no DEB was packed reflecting it. Consider cloning and building. |
Hi all! Can you confirm that 0.9 release from packagecloud.io resolve this problem? |
On Debian/jessie it won't work because we run systemd, not upstart. Also, after packagecloud.io's install script, it installs correctly, but empty distro repo. I've added Ubuntu/trusty manually and apt-get update'd. After this, apt-get install'd, but got the post-install 102 error (from invoke-rc.d and update-rc.d). I'm not familiar with Travis and packagecloud, but I guess the package is only set for Ubuntu. |
Just installed on a clean UbuntuTT VM, just installed lxc+lxctl and lwp from packagecloud.io, it installs and run. You just need to rename lwp.example.conf and reboot/re-run the service. |
@claudyus Debian Jessie install fails as @marcosx86 described because there is no repository for Debian Jessie and the package for Ubuntu Trusty doesn't have a systemd unit. |
@marcosx86 , @flexiondotorg the systemd unit file was propose by @yoav-steinberg in this commit yoav-steinberg@be89ad4 and is now in 0.9 release. |
dpkg: error processing archive /var/cache/apt/archives/lwp_0.8-25-g62597b1_all.deb (--unpack):
subprocess new pre-removal script returned error exit status 102
dpkg: error while cleaning up:
subprocess installed post-installation script returned error exit status 102
Errors were encountered while processing:
/var/cache/apt/archives/lwp_0.8-25-g62597b1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
The text was updated successfully, but these errors were encountered: