Package: ampr-ripd
Version: 2.4.1-1+b2
Please consider creating the directory /var/lib/ampr-ripd on installation.
This way, the encap.txt has a place to go.
Cheers,
Marc
Package: bash-completion
Version: 1:2.11-6
The following does not autocomplete:
mdadm --grow /dev/md126 -l 5 -n 4 -a /dev/nv [tab]
But this works:
mdadm --grow /dev/md126 -l 5 -n 4 --add /dev/nv [tab]
Upon further investigation, it looks like this may be related to an upgrade of
libnet-dns-perl from 0.81-2+b1 to 1.05-1.
See upstream https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7231
Upstream says the bug is closed. I guess I have to wait for the next version
of spamassassin.
Also,
This bug has been dormant for a while. I have not had any problems until this
morning (4am CDT). Then all of a sudden, out of nowhere…
Apr 15 04:12:02 mail spamd[8934]: spamd: got connection over /run/spamd.socket
Apr 15 04:12:02 mail spamd[8934]: spamd: checking message
On 10/24/2015 12:12 PM, László Böszörményi (GCS) wrote:
On Mon, Mar 16, 2015 at 3:10 PM, Marc F. Clemente <m...@mclemente.net> wrote:
One is an Intel i7. Four others are xen virtual machines running on an Intel
Xeon.
On which computers do you get the segfaults? Can you try recent
S
Thanks to the package maintainer, version 0.9.1+git44-gd65c4f8-1 of
fail2ban is available in the experimental repository.
I have tried this a few days on a few different computers, and I have
not had an issue with segfaults in sqlite3.
Others who have segfaults with fail2ban and sqlite3 may
On Mar 16, 2015, at 8:43 AM, László Böszörményi (GCS) g...@debian.org wrote:
On Mon, Mar 16, 2015 at 1:11 PM, Marc F. Clemente m...@mclemente.net wrote:
For what it's worth, I am still getting segfaults in version 3.8.7.4-1.
Multiple different computers, all amd64.
What kind of CPU do you
For what it's worth, I am still getting segfaults in version 3.8.7.4-1.
Multiple different computers, all amd64.
kernel: [413524.044820] fail2ban-server[10402]: segfault at 8 ip
7fbdb22b2350 sp 7fbdb1a5d808 error 4 in
libsqlite3.so.0.8.6[7fbdb22a1000+c3000]
and
kernel:
Package: xen-utils-common
Version: 4.4.1-3
I use xen, and I start some domains using symlinks in /etc/xen/auto. On
startup, the file /etc/init.d/xendomains is supposed to start them. It
does start the domains, but it also throws out a bunch of errors:
/etc/init.d/xendomains: line 135:
On Nov 14, 2014, at 10:05 AM, Noah Meyerhans no...@debian.org wrote:
On Fri, Nov 14, 2014 at 01:53:10PM +0100, Thijs Kinkhorst wrote:
I am not interested in playing bug ping-pong with the libnet-dns-perl
maintainers, though this bug lies with that package. It has already been
fixed
Really? Three weeks and not even an acknowledgment.
As far as I can tell, start-stop-daemon is being called with --name
/usr/sbin/spamd (--name $DAEMON). Maybe it should be --name spamd
(--name $NAME).
Marc
/etc/init.d# diff spamassassin.old spamassassin
54c54
start-stop-daemon
Package: spamassassin
Version: 3.4.0-3
I am having trouble stopping, restarting or reloading the spamassassin
daemon. I don't know it this is a spamassassin bug, or a
start-stop-daemon bug.
Thanks,
Marc
mail:~# ps ax | grep spamd
1304 pts/5S+ 0:00 grep spamd
mail:~#
Package: greylistd
Version: 0.8.8.3
Severity: normal
This package is providing two files in /etc/init.d:
mail:~# dir /etc/init.d/grey*
-rwxr-xr-x 1 root root 1655 Feb 21 2008 /etc/init.d/greylist*
-rwxr-xr-x 1 root root 1784 Jul 27 2013 /etc/init.d/greylistd*
Only one is necessary. Please
Package: exim4-daemon-heavy
Severity: minor
Tags: ipv6
I am in the process of deploying IPv6 on my network. By defauly, spamd listens
on 127.0.0.1:783 and [::1]:783. By defauly, exim connects to spamd on
127.0.0.1:783. I am trying to force exim to connect to spamd at [::1]:783. I
have
This is still happening to me. Basically, the /etc/network/if-up.d/mountnfs
script is being called before the interface is really up. Or maybe the
interface is up, but the IPv6 autoconf did not finish yet. I don’t know...
Specifically, I switched from ipv4 to ipv6 on a computer that was an
Package: spamassassin
Version: 3.4.0-1
Severity: normal
Yesterday I upgraded spamassassin from 3.3.2-7 to 3.4.0-1. I now get a bunch
of lines in my syslog like this:
Feb 21 06:17:56 mail spamd[17742]: auto-whitelist: open of auto-whitelist file
failed: locker: safe_lock: cannot create tmp
On 01/02/2014 11:56 AM, Ian Campbell wrote:
You can select a non-default model use by using the
device_model_version directive in your config.
From what I gather, for now, you MUST select a non-default model, using
something like:
device_model_version=qemu-xen
Package: xen-utils-4.3
Version: 4.3.0-3+b1
Severity: normal
When I try to create an HVW withDevian/xen, I run into trouble. It used to
work, maybe with xen 4.1, but it has never worked since.
Bug 688311 was filed, with the same exact problem. That bug was somehow closed
and no resolution or
Package: xen-utils-common
Version: 4.3.0-3
Severity: normal
# cpuperf-xen
/usr/sbin/cpuperf-xen: 6: exec: /usr/lib/xen-4.3/bin/cpuperf-xen: not found
Exit 127
# ls -l `which cpuperf-xen`
lrwxrwxrwx 1 root root 39 Oct 17 17:24 /usr/sbin/cpuperf-xen -
../lib/xen-common/bin/xen-utils-wrapper*
I
You should post your xlexample.hvm file. Nonetheless, I have something
like this in my file.
device_model_version=qemu-xen
device_model_override=/usr/bin/qemu-system-x86_64
builder='hvm'
Please reply if this does or does not work for you.
I think that Debian's xen hvm support is either
Maybe I need to look more carefully when I type. The error in the log
file that I get is this:
[Aug 13 21:28:48] NOTICE[15119] chan_sip.c: Call from ''
(198.15.80.99:5081) to extension '011972599724974' rejected because
extension not found in context 'default'.
The registration failed is
Package: fail2ban
Version: 0.8.10-3
Severity: normal
I am using fail2ban to monitor asterisk pbx log files. In the log files I get
errors like this one:
[Aug 1 17:17:11] NOTICE[27170] chan_sip.c: Registration from '11
sip:11@192.168.150.51' failed for '188.138.110.45:5178' - Wrong password
And after nearly four years the bug is still open.
These are the errors I get...
TIFFAppendToStrip: Maximum TIFF file size exceeded.
tiff2pdf: Error writing encoded strip to output PDF -.
TIFFAppendToStrip: Maximum TIFF file size exceeded.
TIFFWriteDirectorySec: Error flushing data before
Package: kmod
Version: 9-2
Severity: minor
When I get help from the program with depmod --help I get:
-n, --show Write the dependency file on stdout only
But the documentation man depmod says:
-n --dry-run
All three options work fine and do the same thing, so it's really no big
Package: resolvconf
Version: 1.60
Severity: minor
On bootup, this is what I get...
Sun Sep 25 20:41:40 2011: Starting domain name service...:
bind9run-parts: failed to open directory /etc/resolvconf/update-libc.d:
No such file or directory
Sun Sep 25 20:41:40 2011: run-parts:
Package: tftpd-hpa
Version: 5.1-2
Severity: minor
I am trying to get some debugging output from tftpd. I want to know
what host is requesting what file.
I start the daemon from the command line like so:
in.tftpd --verbose --foreground --listen --user tftp --address
0.0.0.0:69 --secure
More information...
I read the manual (README.Debian.gz) and realized that RSA keys are
deprecated in favor of certificates. So I created and RSA key with
ipsec rsasigkey 2048. I was then able to use RSA keys again.
But I was still having problems with the certificate created by debconf.
Package: resolvconf
Version: 1.58
Severity: minor
The man page for resolvconf(8) mentions the file
/etc/default/resolvconf. I could not find this file after I installed
the package. Does /etc/init.d/resolvconf even look at this file? I
suggest creating /etc/default/resolvconf with options
Package: openswan
Version: 1:2.6.28+dfsg-5+b1
Severity: normal
I am having trouble getting openswan to work with RSA keys. It used to
work, and I have a few computer where ipsec showhostkey works. But now
it doesn't. I don't know if the problem is in my configuration. I
tried purging all the
I don't know if I need to reopen this bug or open a new one, but here
goes...
After yesterday's upgrade, I am having the a new problem with hpnp.monitor.
server:/usr/lib/mon/mon.d# ./hpnp.monitor bertha.tknight.local
Can't locate object method new via package SNMP::Session (perhaps
you forgot
On 11/28/2010 05:34 PM, Andreas Beckmann wrote:
On Tuesday, 21. September 2010 08:30:10 Andreas Beckmann wrote:
On Saturday, 18. September 2010 17:42:19 Marc F. Clemente wrote:
I upgraded to 195.36.31-2 on Aug 26. No problems.
I upgraded to 195.36.31-3 on Sep 3. No problems... Until Sep 12
Package: tzdata
Version: 2010o-1
Severity: minor
I understand that in the United States of America, the preferred way to
set the time zone is America/Chicago, or America/Los_Angeles. That's
all fine, but what about Puerto Rico? As far as as I know, Puerto Rico
is still part of the United
I upgraded to 195.36.31-2 on Aug 26. No problems.
I upgraded to 195.36.31-3 on Sep 3. No problems... Until Sep 12. Now
I start getting random crashes again. This is what Xorg.log says:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x4a1f88]
1: /usr/bin/X (0x40+0x64a99) [0x464a99]
Package: mon
Version: 1.2.0-1
Severity: normal
If I try to run snmpvar.monitor, this is what I get...
server:/usr/lib/mon/mon.d# ./snmpvar.monitor -l ups1
Can't locate object method new via package SNMP::Session at
./snmpvar.monitor line 172.
Exit 2
I add the following line to the
I don't think this is an isolated bug. It is happening to me too.
On my system, I notice that /dev/disk/by-uuid does not contain the dm-0
partition. On another computer, /dev/disk/by-uuid has dm-0 and dm-1 in
it. So maybe when initramfs tries to mount it by UUID, it can't find it
and it
On 08/19/10 14:29, Tormod Volden wrote:
On Tue, Aug 17, 2010 at 9:34 AM, Marc F. Clemente wrote:
~ /usr/lib/xscreensaver/maze
Segmentation fault
Exit 139
Hi Marc, can you please try to get a backtrace?
marc:~ gdb /usr/lib/xscreensaver/maze
GNU gdb (GDB) 7.1-debian
Copyright (C) 2010 Free
On 08/19/10 14:29, Tormod Volden wrote:
~ /usr/lib/xscreensaver/maze
Segmentation fault
Exit 139
(gdb) bt full
#0 0x004068ba in solve_maze (st=0x72e17010) at maze.c:1212
dir = 32767
from = -146359870
ways = 32767
ss = 0x639e90
#1
On 08/16/10 15:17, Jose Luis Rivas wrote:
Could you please tell me how to reproduce it?
~ /usr/lib/xscreensaver/maze
Segmentation fault
Exit 139
I had to leave it for about 12 hours running in a window before it crashed.
Is your only screensaver or does you have it configured to cycle?
Package: xscreensaver-data-extra
Version: 5.11-1
Severity: normal
# dmesg | grep maze
[771455.651377] maze[21281]: segfault at 7f22693318d6 ip 004030c3 sp
7fff35021490 error 4 in maze[40+16000]
[777213.609964] maze[21445]: segfault at 7f81ed037560 ip 004030c3 sp
Package: nvidia-glx
Version: 195.36.24-4
Severity: important
My Xserver crashes occasionally with 195.36.24-4. It used to be stable, but I
think it broke when I upgraded from 190.53-4 to 195.36.24-1. The
crashes appear random; often when the computer is idle. The computer is still
alive
I wonder if this is the same bug as this:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/548362
I have similar issues. I use AMD64. I get random X crashes (but the
computer is still alive). The difference is that I do not have two
GPUs. Also, my crashes are not at
Package: lirc-modules-source
Version: 0.8.3-5
Severity: normal
I use:
m-a -t build lirc-modules
and this is what I get:
...
CC [M] /usr/src/modules/lirc-modules/lirc_i2c.o
/usr/src/modules/lirc-modules/lirc_i2c.c:399: error: unknown field 'id'
specified in initializer
Package: tar
Version: 1.22-1
Severity: normal
I am trying to unpack at bz2 tar file and I get this error:
mc-laptop:~# tar tjf fglrx.tar.bz2
tar: Record size = 8 blocks
modules/
.
. [ stuff omitted ]
.
modules/fglrx/libfglrx_ip.a.GCC4
bzip2: I/O or other error, bailing out. Possible reason
More info:
This works too:
mc-laptop:~# bunzip2 fglrx.tar.bz2 tar xf fglrx.tar \
dd if=/dev/zero of=modules/zero.txt count=1024 \
tar cjf fglrx.tar.bz2 modules tar tjf fglrx.tar.bz2
Go figure... By the way, fglrx.tar.bz2 comes from:
mc-laptop:~# dpkg -S fglrx.tar.bz2
fglrx-source:
Package: luvcview
Version: 1:0.2.4-2
Severity: important
I am trying to run luvcview to see images from a Logitech Quickcam 9000. I use
amd64, but I don't know if that's my problem. Anyway, this is what I get:
luvcview
luvcview 0.2.4
XDM authorization key matches an existing
Aurelien Jarno wrote:
Marc F. Clemente a écrit :
Package: luvcview
Version: 1:0.2.4-2
Severity: important
I am trying to run luvcview to see images from a Logitech Quickcam 9000. I use
amd64, but I don't know if that's my problem. Anyway, this is what I get:
XDM authorization key matches
I can't seem to be able to connect to these sites at all -- they don't
exist in the global DNS, and the IP addresses aren't routable. Can
you reproduce this using some public servers as well?
Try this...
gnutls-cli -s -p 25 mail3.mclemente.net
Cheers,
Marc
wcrg-server:~ gnutls-cli -s -p 25
Simon Josefsson wrote:
Thanks for reporting this, I've solved it with patch:
http://git.savannah.gnu.org/gitweb/?p=gnutls.git;a=commitdiff;h=08fe3bfac8e12e6154dce6a834cdf838eeac3b05
I tried to install the patch, but I had problems. I found socket_bye at
lines 655 and 719. I commented both
Package: libsane
Version: 1.0.19-4
Severity: normal
I use an HP ScanJet 8290 connected via USB. This scanner uses the
avision backend. I tried scanning (with xsane, xscanimage, scanimage,
or gimp-quiteinsane) and I get a segfault. The scanner is recognised
(scanimage -L), but the programs
Package: audacity
Version: 1.3.4-1.1
Severity: wishlist
Please enable JACK on amd64 architectures.
I understand that there are (or there have been) issues with
portaudio19, ringbuffers, memory barries and amd64. I read in
/usr/share/doc/audacity/changelog.Debian.gz
audacity (1.3.4-1)
Marc Haber wrote:
On Wed, Aug 09, 2006 at 11:42:54AM -0500, Marc F. Clemente wrote:
I am seeing this bug with exim version 4.62-4.
To me, it happens with Thunderbird and Mozilla MUAs (on different
computers). It does not happen all the time. If the MUA fails sending
the message, a repeat
Marc Haber wrote:
How did you switch to /dev/urandom? This should not be necessary any
more on current versions of Debian, and - depending on the way the
switch was done - decreases your security of your entire system.
ln -s /dev/urandom /dev/random
I knew it would decrease security of the
Marc Haber wrote:
On Sat, Feb 23, 2008 at 06:22:44AM -0600, Marc F. Clemente wrote:
As a matter of fact, I upgraded the hardware of the mail server last
year. When I did, I reinstalled the OS, and I initially forgot to
switch to urandom. It ran this way for a while and I noticed that I
Someone asked...
Has anyone had any success with going to libpq5_8.3.0-1 from unstable?
Tried it. Still does not work.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On 2008-02-04 Ralph Rößner [EMAIL PROTECTED] wrote:
Just a quick confirm: Same problem for us, downgrading libpq5 to
version 8.2.6-1 makes the problem go away.
On Mon, Feb 04, 2008 at 08:22:22PM +0100, Andreas Metzler wrote:
Is yours also amd64? I do not see this on i386.
I have two (almost)
Package: kino
Version: 1.1.1-1
Severity: normal
Kino fails exporting H.264/FFMPEG. The error is Unknown encoder 'h264' The
problem is in the /usr/share/kino/scripts/exports/ffmpeg_h264_dual.sh file.
The
options -vcodec h264 should actually be -vcodec libx264. The file
ffmpeg_h264.sh has
We believe that the bug you reported is fixed in the latest version of
pixman, which is due to be installed in the Debian FTP archive:
...
libpixman-1-0_0.9.5-3_i386.deb
I use amd64, and I have libpixman-1-0 0.9.5-3 installed. I still can't
use the X server (it crashes within seconds of
Package: xzgv
Version: 0.8-5.1
Severity: grave
Justification: renders package unusable
xzgv: Depends: libglib1.2 (= 1.2.0) but it is not installable
Looks like libglib1.2 does not exist anymore. Please recompile to use
libglib1.2ldbl.
-- System Information:
Debian Release: lenny/sid
APT
Actually, I need to reopen this bug. I just replaced one of my LCD
panels, and the bug reappeared.
Here is my xorg.conf:
Section Module
Loadbitmap
Loaddbe
Loadddc
Loaddri
Loadextmod
Loadfreetype
Loadglx
Brice Goglin wrote:
About a year ago, you reported a bug to the Debian BTS regarding the
mouse pointer not being displayed correctly on the second head of an ATI
board, possibly fixed when using software cursor. Did you reproduce this
problem recently? With Xorg/Etch? With latest
Package: bacula-sd
Version: 2.0.3-2
Severity: minor
From the bacula-sd manpage... The synopsis say bacula-fd.
NAME
bacula-sd - Bacula�s Storage Daemon
SYNOPSIS
bacula-fd [options]
^^^
Marc
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT
Package: dcc-common
Version: 1.3.42-2
Severity: normal
When I try to install dcc-common, this is what I get. Maybe it's missing
square brackets? Same problem on amd64 or i386.
Marc
# apt-get --reinstall install dcc-common
Reading package lists... Done
Building dependency tree... Done
0
Upon further investigation, I think that /dev/MAKEDEV is SUPPOSED to be
there! Please look at the thread for bug 387995. Run the following
command to put the symlink back in /dev/
apt-get --reinstall install makedev
Marc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: bluez-utils
Version: 3.1-4+b1
Severity: important
The postinst file tries to run ./MAKEDEV from the /dev directory. My
system has a /sbin/MAKEDEV but no /dev/MAKEDEV. I have both udev and
makedev packages installed.
Marc
Setting up bluez-utils (3.1-4+b1) ...
Creating device nodes
Incidentally, the problem goes away if I use
Option SWcursor on
for the second head.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I am seeing this bug with exim version 4.62-4.
To me, it happens with Thunderbird and Mozilla MUAs (on different
computers). It does not happen all the time. If the MUA fails sending
the message, a repeat attempt will eventually succeed.
I tried connecting manually with:
gnutls-cli --port
By the way, I get the same result, and I am running AMD64 as well.
Marc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: ppp
Version: 2.4.4rel-2
The /etc/ppp/ip-up.d/usepeerdns script checks for the $USEPEERDNS
environment variable before messing with /etc/resolv.conf.
I think that the /etc/ppp/ip-down.d/usepeerdns script should also
check $USEPEERDNS before unmessing /etc/resolv.conf. What
Package: openswan
Version: 2.4.4-3.1
The file /usr/lib/ipesec/_updown tries to load
/etc/sysconfig/pluto_updown. This file does not exist in Debian. Is
this a bug? Maybe it should try something in /etc/default/? Is the
_updown file even used in debian?
Sorry if this is a bogus bug
Robert Millan wrote:
Then I think the right fix would be to attempt a download of x86_64-pc-linux-gnu
binary, and if that fails fallback to i386-pc-linux-gnu. In that situation
libc6-i386 wouldn't be needed in Depends (maybe Recommends instead).
Or maybe this alternative... Boinc checks to
Robert Millan wrote:
TTBOMK, no boinc projects are providing core binaries for amd64. So our only
hope of making this package useful on that platform is requesting i686 ones
instead. Patch attached.
I disagree. I run a 64 bit Seti client on my amd64. I think that's
useful enough. The 64
Package: mozilla-browser
Version: 2:1.7.12-1
Severity: minor
This sounds a lot like bug #305280.
marc:~# dpkg -S mozilla-1.7.11
mozilla-browser: /usr/bin/mozilla-1.7.11
marc:~# dpkg -l mozilla-browser
Desired=Unknown/Install/Remove/Purge/Hold
|
Package: openoffice.org2
Version: 1.9.125
The debian/control file does not include the amd64 architecture. Can
you please fix this minor oversight. Sample patch included.
Thanks,
Marc
--- openoffice.org2-1.9.125/debian/control 2005-09-18 12:16:51.0 -0500
+++
package: xine-ui
version: 0.99.3-1.1
On amd64, xine-ui version 0.99.3-1 depended on libcurl3. Now, on
version 0.99.3-1.1 it depends on libcurl3-gnutls. Why the change (not
documented in changelog.Debian.gz)? The problem is that libcurl3-gnutls
conflicts with libcurl3. And clamav depends
Happens to me in version 1.1.4-7
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The architecture-dependant build environments that are meant to be set
up in debian/rules file are not actually set up. DEB_BUILD_ARCH
variable is not anywhere in this file.
Actually, DEB_BUILD_ARCH is indeed set up correctly on my amd64. I
think it gets set by dpkg-architecture.
The
Any chance somebody can post a diff for debian/rules? At least I can
recompile it myself and end up with something useful.
Thanks,
Marc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: kernel-source-2.6.11
Version: 2.6.11-7
The kernel fails to compile with gcc4.0. I include the error. I found
a patch, but I have not tried it. It was at:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0503.1/2428.html
Thanks,
Marc
...
CC [M] drivers/char/generic_serial.o
Package: xine-lib
Version: 1.0.1-1
Package aalib1-dev has been replaced by libaa1-dev.
Marc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: kino-timfx
Version: 0.2.2-2
This dependency makes kino-timfx not installable on my system.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: freeglut3
Version: 2.2.0-8
I think package libglu1 has been renamed to libglu1c2. Rebuilding the
package should fix the problem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: setiathome
Version: 3.08-4
It looks like alien.ssl.berkeley.edu is not correct anymore.
As a matter of fact, it looks like you can't get the old seti client
software anymore. All I can find is the boinc software.
Maybe this package is no longer needed...
Marc
marc:/home/marc#
Package: clamav
Version: 0.86.1-2
clamav packages depend on libgmp3. I think this has been renamed to
libgmp3c2.
Marc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
83 matches
Mail list logo
