Package: libnet-amazon-s3-perl
Version: 0.53-1
Severity: minor
Tags: patch
As seems to often be the case, attempts to use a library beyond its stated
capabilities results in discoveries of incomplete coding.
I do recognize there is a newer version of this library, however looking over
it
Package: libnet-amazon-s3-perl
Version: 0.50-1
Severity: normal
I don't exactly consider myself a normal user of this package (I'm only using
Net::Amazon::S3::HTTPRequest,
and not using the http_request method), but I'm seeing the following error in
my diagnostic results:
Undefined
Package: libsoap-lite-perl
Version: 0.710.08-1
Severity: normal
Tags: patch
Attempt to smoketest a mod_perl installation using this package resulted
in a 500 error in a web browser and the following error in apache2.err:
Can't locate auto/Apache2/Const/HTTP_BAD_RE.al in @INC (@INC contains:
the
regular cron emails to make sure the daily warnings are gone, but otherwise
I believe your fix corrected this situation. Thank you for your time and
patience.
-Original Message-
From: Micah Anderson [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 11:00 PM
To: Erik Anderson
I have spent some time trying to get X working again as per this bug, but it
has been some time since I have been in here and many of the packages have
changed since then.
I have not yet successfully gotten an XDMCP session running yet, but I
cannot say whether it is related to this bug or one of
I've probably said this before, but I will try to get into this and try it
out by the end of the week. I haven't been using X11 for some time due to
this issue and it would be good to get a GUI running again. There was also
a suggestion posted earlier as a possible workaround that I had not yet
Package: backupninja
Version: 0.9.4-3
Severity: normal
This issue was exposed after the weekly dselect/testing update done last
Friday. Since the update, I have been receiving WARNING emails stating
that the ldif export had failed. A debugging run of backupninja showed
a call to slapcat,
After reading this email thread after finding it in the Changelog, I don't
think i want to open a bug on this, but...
If I hadn't seen the word 'qmail-src' scroll off my screen when i came back
during an upgrade, I would have no knowledge that my qmail package was out
of date and needed
I just ran into this issue on upgrade to 251-5. My password
does have two hyphens in it, package refuses to configure at this point. My
current configuration file is still working so this isnt a major problem
to me, but in the meantime I have a partially-corrupt installation.
I realize
15, 2006 2:09 PM
To: Erik Anderson; [EMAIL PROTECTED]
Subject: Re: kdm: will no longer start (using Xvnc, errno 97)
can you paste the answer from /sbin/ifconfig to us please ?
if you see lines like adr inet6: ... then you have ipv6 configured on
the machine, and you have to force kdm to listen
Package: mysql-server-5.0
Version: 5.0.18-7
Severity: normal
Note: this may be a duplicate of #343639, but too many people have tried
to take over bugs that I've seen, so I won't comment while the moreinfo
bit is on there. Plus there is more than one bug reported in the last
couple of months,
I have reported a bug similar to this one, it may be helpful if you could
verify that our symptoms are the same.
Could you do a CHECK TABLE, REPAIR TABLE, CHECK TABLE on your problematic
table? I would like to check to see that (1) the REPAIR TABLE always
succeed, and (2) the CHECK TABLE always
Package: kdm
Version: 4:3.5.1-1
Severity: important
I am no longer able to log into my debian linux box using Xvnc, the
following log messages result with any attempt:
kdm[2181]: XDMCP socket creation failed, errno 97
kdm[2181]: Internal error: config reader supplied incomplete data
kdm[2181]:
13 matches
Mail list logo
