Judging from this bug and the statement that Arte regularly changes its
streaming system, this package is a clear candidate for volatile for
Squeeze+1.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o
This comes from distutils. Apparently newer versions install
Python files into site-packages and data files into
dist-packages. debian/rules of openerp-server only moves the
site-packages subdirectory to /usr/lib/openerp-server.
The solution is to use --install-layout=deb when calling setup.py
(or
/etc/init.d/mysql is part of the package mysql-server-5.1. You
only have mysql-server-core-5.1 installed, so I suspect the
script remains from a removed, but not purged package.
mysql-server-5.1 is correctly depending on mysql-client-5.1, but
mysql-server-core-5.1 is not. I think the proper way to
I checked some of the other Ruby packages and none of them used
versioned dependencies. I agree that it might be a good idea to
use versioned dependencies, but if so then all packages should
have them.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubs
I think that generally disabling SysRq while xscreensaver is running is not a
good idea. It will prevent the use of other commands that might be useful if the
system is behaving troublesome.
I think that a setuid helper specifically for this task is the proper solution,
if it can be ensured that i
On Tue, Dec 01, 2009 at 04:42:24PM +0100, Toni Mueller wrote:
> You are more than welcome to help preparing a useful update to this
> package (please contact me privately), but there's much, much more to
> it than simply fixing the paging bug.
What other regressions have been introduced by the sec
Is this going to be fixed via stable-security? If nothing happens here, I will
prepare a new package and hand it to the security team.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Shouldn't this also be fixed for stable? It was a serious regression introduced
by a security patch.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Wed, Nov 26, 2008 at 08:05:00AM +0100, Yves-Alexis Perez wrote:
> btw, in init-function, below pidofproc there's a comment:
> # start-stop-daemon uses the same algorithm as "pidofproc" above.
I think that's the proper way to go. Quoting the pidof manpage: "If the
system has a start-stop- daemon
I suspect this is still not fixed. On a freshly installed Lenny system
of mine, portmap refuses to start stating "Already running". Adding
debug output to the init script shows that $(pidofproc portmap) returns
the PID of the shell running the init script ($$).
pidofproc falls back to pidof when t
10 matches
Mail list logo
