Dear chaepsoft customer!
We have update our programs list, now we have more and new version programs.
Our full catalog with 1500 fresh software titles
http://Datamedia.rubikonaj.com/2/p/
With best regards,
Chaepsoft Manager
Jason Amembers
Hello again,
I got the sites back up, but still have a question. Here's what I did.
Copied /etc/apache/httpd.conf over every other httpd.conf file I could
find, including ones in /usr/share/apache/default-configs/apache-ssl and
/usr/share/apache/default-configs/apache-perl as well as
/etc/apache-
Hi,
I run Debian testing. I had Apache 1.3.29 installed and working fine,
using name-based virtual hosting to host several websites.
I upgraded to 1.3.31 this morning and it changed the default document
root back to /var/www because now ALL of my virtual hosts point to the
index.html file in /var
EUROPARTNER Group Poland Spółka z o.o. 04-028
Warszawa, Aleja Stanów Zjednoczonych 53tel: 022 810 56 82, fax: 022
810 66 73, e-mail: [EMAIL PROTECTED],
www.europartnergroup.plNIP: PL
1132461419IMPORTERZY WSCHODNIWschodnioeuropejski Bank Ofert Handlowych
EuropartnerRosja, Ukraina, Biał
Your message dated Sun, 1 Aug 2004 16:08:21 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to re
Your message dated Sun, 1 Aug 2004 14:41:07 +0100
with message-id <[EMAIL PROTECTED]>
and subject line NotABug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen th
* Christian Eichert ([EMAIL PROTECTED]) wrote :
> I updated mailman 2.1.4-5 from the apt
> I updated apache2 2.0.50-5
>
> Everything looks OK except for one thing: when a URL like,
>
> http://myhost/mailman/listinfo
>
> is requested, 'Apache2' locates the file (return code = 200) but wa
Just a short notemmi,
Did you recieve my notificationfrom last week? I'm excited to tell you
that you could be approved for a home loan at 3.70% . Chances are this is
much better than your current home-loan
Here are your tracking links, use either one: Or
http://aucbimo.info/prime/Timpana/index.
Processing commands for [EMAIL PROTECTED]:
> severity 262642 grave
Bug#262642: bash: coredump on firehol
Severity set to `grave'.
> severity 262438 grave
Bug#262438: bash: bash 3.0 segfault running the 'firehol' script.
Severity set to `grave'.
> merge 262642 262438
Bug#262438: bash: bash 3.0 se
Your message dated Sun, 01 Aug 2004 03:47:11 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#257108: fixed in apache 1.3.31-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 01 Aug 2004 03:47:11 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#257566: fixed in apache 1.3.31-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 01 Aug 2004 03:47:11 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#258602: fixed in apache 1.3.31-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 01 Aug 2004 03:47:11 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#259169: fixed in apache 1.3.31-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 01 Aug 2004 03:47:11 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#262582: fixed in apache 1.3.31-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Accepted:
apache-common_1.3.31-3_i386.deb
to pool/main/a/apache/apache-common_1.3.31-3_i386.deb
apache-dbg_1.3.31-3_i386.deb
to pool/main/a/apache/apache-dbg_1.3.31-3_i386.deb
apache-dev_1.3.31-3_all.deb
to pool/main/a/apache/apache-dev_1.3.31-3_all.deb
apache-doc_1.3.31-3_all.deb
to pool/
There are disparities between your recently accepted upload and the
override file for the following file(s):
apache-perl_1.3.31-3_i386.deb: package says priority is optional, override says
extra.
Either the package or the override file is incorrect. If you think
the override is correct and the
apache_1.3.31-3_i386.changes uploaded successfully to localhost
along with the files:
apache_1.3.31-3.dsc
apache_1.3.31-3.diff.gz
apache-doc_1.3.31-3_all.deb
apache-dev_1.3.31-3_all.deb
apache_1.3.31-3_i386.deb
apache-ssl_1.3.31-3_i386.deb
apache-perl_1.3.31-3_i386.deb
apache-dbg_1.
tags 262582 + patch
thanks
--- /usr/sbin/apache-modconf~ 2004-06-24 22:40:22.0 +0200
+++ /usr/sbin/apache-modconf2004-08-01 09:12:57.0 +0200
@@ -65,7 +65,7 @@
fi
done
- cd -
+ cd - >/dev/null
if [ "$err" = "1" ]; then
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
apache_1.3.31-3.diff.gz
apache_1.3.31-3.dsc
apache_1.3.31-3_i386.deb
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.
If no .changes file arrives within 23:2
Processing commands for [EMAIL PROTECTED]:
> tags 262582 + patch
Bug#262582: BASH3.0 BREAKS APACHE! THANKS BASH MAINTAINER.
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administra
Your message dated Sun, 1 Aug 2004 08:10:03 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line no information after one month
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Sun, 1 Aug 2004 08:06:40 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Closing.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to r
Processing commands for [EMAIL PROTECTED]:
> clone 262582 -1
Bug#262582: BASH3.0 BREAKS APACHE! THANKS BASH MAINTAINER.
Bug 262582 cloned as bug 262619.
> reassign -1 bash
Bug#262619: BASH3.0 BREAKS APACHE! THANKS BASH MAINTAINER.
Bug reassigned from package `apache-common' to `bash'.
> retitle
On Thu, 29 Jul 2004 [EMAIL PROTECTED] wrote:
> Sorry to bother, but I'm having trouble with modules-config.
>
> Recently, I couldn't update libapache-mod-ssl. I tracked the problem
> down to it's postinst script, which calls "modules-config apache enable
> mod_ssl".
>
> When I try running "modules
Processing commands for [EMAIL PROTECTED]:
> retitle 262582 BASH3.0 BREAKS APACHE! THANKS BASH MAINTAINER.
Bug#262582: apache-common: apache-modconf doesn't accept correct syntax. dpkg
reported error status 128 when installing libapache-mod-perl
Changed Bug title.
> stop
Stopping processing here
retitle 262582 BASH3.0 BREAKS APACHE! THANKS BASH MAINTAINER.
stop
On Sun, 1 Aug 2004, Fabio Massimo Di Nitto wrote:
>
> Hi Philipp,
>
> On Sat, 31 Jul 2004, Philipp Bliedung wrote:
>
> > Package: apache-common
> > Version: 1.3.31-2
> > Severity: serious
> > Justification: apache-modconf doesn't
[EMAIL PROTECTED]"(B
$B!!(B
$B!!K\F|$N(B[$B$a!<$k$^$,$N([EMAIL
PROTECTED](B]$B$O!]!Z=PMh$k!&$G$-$k!<#2#0:P0J>e$NCK=w$J$i=PMh$k![(B
$B!!(B
$B!!:#$NG:$_$O!&!&!&[EMAIL
PROTECTED]|1_$G2r7h=PMh$k!*L\E*$K
Hi Philipp,
On Sat, 31 Jul 2004, Philipp Bliedung wrote:
> Package: apache-common
> Version: 1.3.31-2
> Severity: serious
> Justification: apache-modconf doesn't accept correct syntax
>
> *** Please type your report below this line ***
>
> apache-common: apache-modconf doesn't accept correct syn
28 matches
Mail list logo
