Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Nokao wrote:So my questions are:
When it will be supported ?
To understand why this question is unanswerable, you need to understand something about Debian release cycles. For the foreseeable future, Debian developers are focused on bug fixes for Wheezy, not on porting SNS (Shiny New crap) to sid.
Nokao wrote:How can I install it in a Stable system forcing apt ?
You can't. If you're not comfortable compiling from source, then you'll need to wait it out.
But before you even consider such an undertaking, you might find it worth your time to convince yourself that you absolutely, positively need something that's available only in the 2.4 branch.
I run Debian unstable on my laptop and most of my servers. I have one production web server that runs Debian stable instead, but mostly I can deal with any day-to-day glitches that come up using Debian unstable
"I am not fine with it, so there is nothing for me to do but stand aside." M.D.
Nokao wrote:How can I install it in a Stable system forcing apt ?
You can't. If you're not comfortable compiling from source, then you'll need to wait it out.
But before you even consider such an undertaking, you might find it worth your time to convince yourself that you absolutely, positively need something that's available only in the 2.4 branch.
I compiled in the past, but this is a very important server and I don't want to screw up things.
The function I'm searching for in Apache 2.4 is ErrorLogFormat, that helps to format errors log in php. Because I have many websites in a single virtual server, I can't understand which one is causing errors in the current log.
So, I'll just surrender and wait, however you can't "tar everyone with the same brush" saying that Apache 2.4 is SNS.
But please, wasn't there an apt-get force upgrade somewhere or a way to make exeptions importing testing stuff into stable releases ?
Nokao wrote:But please, wasn't there an apt-get force upgrade somewhere or a way to make exeptions importing testing stuff into stable releases ?
Trying to mix Stable with Testing/Unstable/Experimental is an Amazingly Bad Idea. Search these forums to find multiple horror stories from people who have tried.
And trying to do it on a production server is just flat stupid.
I can't escape my sneaking suspicion that you're going to try to do it anyway. And then you'll come back here when your server is totally FUBAR and ask please, isn't there just some easy, one-click way to undo all the damage??
dasein wrote:
I can't escape my sneaking suspicion that you're going to try to do it anyway. And then you'll come back here when your server is totally FUBAR and ask please, isn't there just some easy, one-click way to undo all the damage??
And the answer will still be "no."
*Nokao disappear in the dark*
*Nokao's skill sneaking is raised to 100%*
*Nokao's attempt to FUBAR his server was discovered by dasein*
*you hear the noise of an exploding server*
*you die*
Nokao wrote:The function I'm searching for in Apache 2.4 is ErrorLogFormat, that helps to format errors log in php. Because I have many websites in a single virtual server, I can't understand which one is causing errors in the current log.
You can already set different logfiles for each vhost.
But by "virtual server" it sounds like you mean "virtual host" and all your "many sites" are hanging off one CMS instance ...
Nokao wrote:The function I'm searching for in Apache 2.4 is ErrorLogFormat, that helps to format errors log in php. Because I have many websites in a single virtual server, I can't understand which one is causing errors in the current log.
You can already set different logfiles for each vhost.
But by "virtual server" it sounds like you mean "virtual host" and all your "many sites" are hanging off one CMS instance ...
Exactly, so there is no solution to the problem,
unless waiting for Apache 2.4 to became a stable software for Debian.
And it is, stable, but Debian is very famous for it's prudence, so I'll be waiting so long.
