On Sun, Apr 29, 2012 at 2:02 PM, Jérémie Burtin
wrote:
> On 24/04/12 19:09, Charlie Smotherman wrote:
>>
>> yes but ampache does depend on libapache2-mod-php5 which will pull in
>> apache2 even though the package does not directly depend on apache2
>
> I disagree, it depends on libapache2-mod-php5
On 24/04/12 19:09, Charlie Smotherman wrote:
yes but ampache does depend on libapache2-mod-php5 which will pull in
apache2 even though the package does not directly depend on apache2
I disagree, it depends on libapache2-mod-php5 | php5-cgi | php5 .
However with the upcoming Apache2.4 transitio
2012/4/24 Jérémie Burtin :
> On 24/04/12 15:54, Charlie Smotherman wrote:
>>
>> On Tue, Mar 27, 2012 at 2:11 PM, Jeremie BURTIN
>> wrote:
>> Jeremie,
>>
>> Thanks for the bug report.
>
> You're welcome.
>
>> Although Ampache is capable on running on just about any webserver,
>> Ampache's packagin
On 24/04/12 15:54, Charlie Smotherman wrote:
On Tue, Mar 27, 2012 at 2:11 PM, Jeremie BURTIN
wrote:
Jeremie,
Thanks for the bug report.
You're welcome.
Although Ampache is capable on running on just about any webserver,
Ampache's packaging does not support the installation on nginx. The
pac
On Tue, Mar 27, 2012 at 2:11 PM, Jeremie BURTIN
wrote:
Jeremie,
Thanks for the bug report.
Although Ampache is capable on running on just about any webserver,
Ampache's packaging does not support the installation on nginx. The
packaging only supports the installation on Apache2, Lighttpd and
My
Package: ampache
Version: 3.6-alpha1+dfsg-3
Severity: important
Upgrade from ampache 3.6-alpha1+dfsg-2 -> 3.6-alpha1+dfsg-3 failed.
Web server is nginx, not apache2.
Errors were encountered while processing:
ampache
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to ins
6 matches
Mail list logo
