The "fix" to use_ipv6.pl breaks installations where lighttpd is running on
a port other than port 80. In our case, we have apache on port 80, and
lighttpd running on port 83. The upgrade to 1.4.25-2 failed because
apache is already listening on port 80.
--
Ken Bowley
System Adm
If k7 is going to be dropped, can the linux-image-2.6-k7 package depend on
linux-image-2.6-i686 to make upgrading easier?
Ken
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: apache2
Version: 2.2.3-3
Followup-For: Bug #396631
I am also seeing this bug and the error.log shows a segfault when
attempting to load a file. Directory lists work fine.
[Tue Nov 07 10:19:58 2006] [notice] child pid 10999 exit signal Segmentation
fault (11)
-- System Information:
De
Package: uprecords-cgi
Version: 1:0.3.7-3
Severity: normal
Tags: patch
When uprecords is called as uprecords.cgi, it will look in the current
directory for the uprecords.conf, uprecords.header and uprecords.footer
files rather than /etc/uprecords-cgi/.
--- src/uprecords.c 2006-08-17 13:07:34.
Package: lighttpd
Version: 1.4.11-7
Severity: grave
Justification: renders package unusable
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Johann Friedrich <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: lighttpd
Package: openssh-server
Version: 1:4.2p1-5
Severity: normal
After a day of beating my head against a wall trying to get sshd to log
bad logins as it does on my Slackware box, I just realized that it was
the Debian specific package that prevented sshd from logging bad login
attempts. I would like
Package: rails
Version: 0.14.3-1
Severity: important
The upstream ticket for this bug is
http://dev.rubyonrails.org/ticket/2996
It was fixed in http://dev.rubyonrails.org/changeset/3183
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Package: geotoad
Version: 3.7.5-2
Severity: wishlist
new version of geotoad has been available since 2005-17-07 with updates
for changes to geocaching.com website, although the patch from 3.7.5-2
for details.rb still needs to be applied.
-- System Information:
Debian Release: testing/unstable
A
Package: geotoad
Version: 3.7.5-1
Severity: grave
Justification: renders package unusable
I'm not sure if it's the recent changes/upgrades to geocaching.com or
just the caches that I have been looking at recently, but geotoad can no
longer parse the cache information properly. Here is a diff for
9 matches
Mail list logo
