Package: memcachedb
Version: 1.2.0-2
Severity: normal
The package doesn't contain a man page for /usr/bin/memcachedb
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel:
Package: iceweasel
Version: 3.0.6-1
Followup-For: Bug #463757
Iceweasel crashed when visiting
http://github.com/clivecrous?r=vultures-screenshots;a=headblob;f=/bigroom-10-26-05.png
It repeat crashing if session is restored after restart
Bug-buddy report followes:
System: Linux 2.6.26-1-686 #
Package: spread
Version: 3.17.4-2+b1
Severity: important
In /etc/init.d/spread the config file to use is specified as
/etc/spread.conf whereas the real path is /etc/spread/spread.conf
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable
sloader trouble if a web application ships another
version of the library.
- -billy.
- --
Philipp Meier - [EMAIL PROTECTED]
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG
Package: bzip2
Version: 1.0.3-1
Severity: grave
Justification: renders package unusable
bzip2 fails to install:
error in control file: `Index' value missing for type HTML at
/usr/sbin/install-docs line 641, line 13.
-- System Information:
Debian Release: testing/unstable
APT prefers unstabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Line 73 in texinfo.postint reads "...update_ls_files" and must read
"...update_lsr_files".
- -billy.
- --
Philipp Meier - [EMAIL PROTECTED]
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
Package: hardware-monitor
Version: 1.2.1-2
Followup-For: Bug #269978
After reading this tread I understand the intetion behind the current
behaviour. I find this highly unintuitive and annoying. Is there a
chance to have an option to enable a "sync view"? The argument of memory
beeing a straight
Patch applied. New relase was 5.1.5rc1-4 uploaded to mentors.debian.net
and is waiting for a sponsored upload.
--
Philipp Meier - [EMAIL PROTECTED]
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
signature.asc
Description: This is a digitally signed
pkg-java-maintainters which
maintain tomcat4. Please could the tomcat maintainers comment on this.
Is there any interrest in splitting the jasper implementation from the
tomcat package?
-billy.
--
Philipp Meier - [EMAIL PROTECTED]
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
signature.asc
Description: This is a digitally signed message part
close 5.1.5rc2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
close 5.1.5rc2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
close 5.1.5rc2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
closed 5.1.5rc2
thanks
Close in new package release by disabled validation.
--
Philipp Meier - [EMAIL PROTECTED]
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
signature.asc
Description: This is a digitally signed message part
moreinfo
thanks
New package release 5.1.5rc2 should fix this issue. Please provide more
information.
thanks.
--
Philipp Meier - [EMAIL PROTECTED]
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
signature.asc
Description: This is a digitally signed message
closed 5.1.5rc2
thanks
Dependencies are fixed in jetty-5.1.5rc2
--
Philipp Meier - [EMAIL PROTECTED]
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
signature.asc
Description: This is a digitally signed message part
or if your restart tomcat from the shell.
-billy.
--
Philipp Meier - [EMAIL PROTECTED]
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
signature.asc
Description: This is a digitally signed message part
Am Montag, den 22.08.2005, 19:30 +0200 schrieb Johannes (groups):
> Philipp Meier wrote:
> > This is due to a wrong configuration of the servlet and jsp libaries
> > in /etc/jetty/start.conf. Please check
> > if /usr/share/java/servlet-api.jar and /usr/share/java/jsp-api
e/java/servlet-api.jar and /usr/share/java/jsp-api.jar are
included correctly. The jar names had changed with libservlet-2.4-java
which does not conflict with jetty-5.0.0-2.1.
BTW, a new upstream release of jetty (5.1.4) is beeing uploaded in the
next days.
--
Philipp Meier - [EMAIL PROTECTED]
A: B
Package: libapache2-mod-jk2
Version: 2.0.4-3
Severity: grave
Justification: renders package unusable
If a context is specified for a uri: apache constantly segfaults. The
worker in case connects to a jetty instance.
workers2.properties is:
---
Package: apt
Version: 0.6.38
Severity: minor
The man page for sources.list contains an example "unstable/binary-3866"
instead of "unstable/binary-i386".
-- Package-specific info:
-- (no /etc/apt/preferences present) --
-- (/etc/apt/sources.list present, but not submitted) --
-- System Info
This bug will be fixed in the next debian package release. It will take
some days until I can prepare a new package, though. The workaround I
recommend is to add
property=org.mortbay.xml.XmlParser.NotValidating=true
in /etc/jetty/start.config
--
Philipp Meier - [EMAIL PROTECTED]
A: Because it
Package: db4.3-util
Version: 4.3.27-2
Severity: normal
Debian policy requires a manpage for every executable in /usr/bin.
Manpages are missing from db4.3-util. db4.3-doc does not provides
manpages either.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'uns
Package: apt-proxy
Version: 1.9.26
Severity: normal
/etc/init.d/apt-proxy will not work with dash:
/etc/init.d/apt-proxy: 19: Syntax error: "(" unexpected
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.
Am Sonntag, den 20.02.2005, 14:33 -0800 schrieb Debian Bug Tracking
System:
> Hi Dalibor, Philipp,
>
> Can you try to reproduce the bug you reported?
>
> I think your bug should be closed by the new upload of kaffe.
The following version does not show the reported behaviour:
2:1.1.4.PRECVS8-2
Package: wondershaper
Version: 1.1a-4
Severity: important
Wondershaper contains bashisms, it does not work with dash. The
following tests in the top of the script are broken:
if [ $# == 0]; then
I don't know how to fix them. Workaround is to use bash with
wondershaper.
-- System Information:
D
Am Samstag, den 22.01.2005, 21:21 -0500 schrieb Chet Ramey:
> Matthias Klose wrote:
> > I agree with the bug submitter ...
>
> I probably would too, if I were fluent in German, but since the message
> comes from whatever translation the system has for sys_siglist[SIGALRM],
> I can't see how it's a
Package: zsh
Version: 4.2.3-1
Severity: important
Tags: l10n
The completion functions for svn build the command list based on the
output of the svn commands. This parsing fails for non-english locales.
A fix will be either to change the parsing regexes or to call
the svn command with locale "C".
Package: bash
Version: 3.0-13
Severity: minor
Tags: l10n
The german translation of the message "Alarm clock" if a SIGALARM is not
trapped reads "Der Wecker klingelt" is misleading. Actually the english
message is not helpful either. A better translation would be
"Alarmsignal" or the like.
[EMAIL
28 matches
Mail list logo
