Package: ddclient
Version: 3.8.1-1
Hi, the freedns support of ddclient 3.8.1 depends on the module
Digest::SHA1, but the module is sometimes named Digest::SHA (for example in
Wheezy).
In order to make the freedns support of the package also work in Wheezy, a
small patch is needed, which is
the same thing happened to me a while ago.
i thought it might only be a bad joke (reading about restart being
deprecated and losing network connection / ssh access at the same time),
especially because it works just fine with my RHEL-servers.
--
To UNSUBSCRIBE, email to
in my case the problem was caused due to the swap device being listed in
/etc/initramfs-tools/conf.d/resume . it would be nice if there was some hint
when the swap removal fails because of this.
Package: host
Severity: important
When using host to determine the PTR records of an IP it gives an error message
if multiple PTR records are found:
:~# host 83.137.131.82
83.137.131.82 PTR record not found
This works fine with bind9-host
-- System Information:
Debian Release: 5.0.3
APT
been fixed in unstable with the release 1:1.1.11-2.
Thanks,
Fabio
E-Mail-Nachricht-Anlage
Weitergeleitete Nachricht
Von: Martin Jürgens m...@jgs-wg.de
An: Debian Bug Tracking System sub...@bugs.debian.org
Betreff: dovecot-common: /etc/init.d/dovecot stop does
Package: dovecot-common
Version: 1:1.0.15-2.3+lenny1
Severity: important
/etc/init.d/dovecot stop does not stop dovecot, the process remains running.
I rated this as being important because it prevents security updates for
dovecot from operating because it is not restarted when dpkg calls that
Package: lvm2
Version: 2.02.39-7
Severity: normal
lvremove fails to remove my swap LV, although it is not mounted and not
mentioned in /etc/fstab:
x:~# free -m
total used free sharedbuffers cached
Mem: 498410 88 0
Package: kernel
Severity: important
My system (RHEL 5.4 KVM guest) got unaccessible (*very* high cpu load). After
rebooting it and checking the logs, I found out that a kernel issue appears:
ct 4 02:02:14 mubuntos3 mount.davfs: open files exceed max cache size by 685
MiBytes
Oct 4 02:07:38
Package: asterisk
Version: 1:1.2.13~dfsg-2
Tags: security
In etch, there is version 1.2.13 of Asterisk, which contains multiple
security flaws:
http://asterisk.org/node/48319
Patch:
http://svn.digium.com/view/asterisk/branches/1.2/channels/chan_sip.c?r1=56230r2=57475
Package: pgadmin3
Version: 1.4.3-2
The pgadmin team released pgadmin version v1.6.2 on 8th January. It would be
nice to have the newer version available in unstable.
The announcement can be found at http://www.pgadmin.org/news.php.
Thanks!
Martin
signature.asc
Description: This is a
Package: asterisk
Version: 1:1.2.16~dfsg-1
Asterisk does not create /var/run/asterisk directory if not existent.
Diff which should solve that:
diff -u asterisk-1.2.16~dfsg/debian/asterisk.init
asterisk-1.2.16~dfsg/debian/asterisk.init
--- asterisk-1.2.16~dfsg/debian/asterisk.init
+++
Package: asterisk
Version: 1:1.2.16~dfsg-1
Some Debian based distros (like Ubuntu) have /bin/sh linked to /bin/dash
instead of to /bin/bash.
Thus, it would be much more appreciated if contrib/scripts/safe_asterisk said
#!/bin/bash instead of #!/bin/sh at the beginning.
An other option would
Package: asterisk
Version: 1:1.2.16~dfsg-1
The debug option commented out by default in /etc/default/asterisk is:-
PARAMS=-D -g -vvv
This causes Asterisk to fail:-
Starting Asterisk PBX: /usr/sbin/asterisk: invalid option -- D
This needs to be changed to:-
PARAMS=-d -g -vvv
Okay, I did not really know what it is. -D should be removed (or
replaced) then from /etc/default/asterisk as it does not seem to work
with the current Asterisk:
Starting Asterisk PBX: /usr/sbin/asterisk: invalid option -- D
Thanks,
Martin :)
signature.asc
Description: This is a digitally
Hi!
How could that happen?
When using a TMPFS for /var/run, the init script has to manage the
directory creation. (This is not the default case in Debian)
+if [ ! -e `dirname $PIDFILE` ];then
Speaking of posix-shell-strictness: is '[ -e' valid?
At least, it works for me. But you should
Package: erlang
Version: 1:11.b.2-4
The crypto module is not working when compiling erlang with gcc 4.1:
[EMAIL PROTECTED]:~/src/ejabberd111/src$ erl
Erlang (BEAM) emulator version 5.5.1 [source] [async-threads:0]
[kernel-poll:false]
Eshell V5.5.1 (abort with ^G)
1 crypto:start().
exec: 1: ok
2
I use Ubuntu, in which the bug appears with GCC 4.1 and not with GCC
4.0.
That's why I assumed that the same bug appears in Debian.
The problem is not that Erlang does not start. Instead, it is that the
crypto module does not load correctly:
*
[EMAIL PROTECTED]:~$ erl
Eshell V5.5.1 (abort
I can not fix and / or reproduce this bug but I'd like to add that the
bug has been fixed in Ubuntu:
https://launchpad.net/ubuntu/+source/mouseemu/+bug/67954
Martin
signature.asc
Description: This is a digitally signed message part
Package: xmoto
Version: 0.2.2-1
Severity: wishlist
Opening xmoto replays currently is a mess: You have to open a
Terminal, cd to the directory where the downloaded replays are stored
and then type xmoto -replay REPLAYFILE.rpl.
The file type .rpl should be associated with xmoto -replay so that
19 matches
Mail list logo
