Hi,
I think these are just rounding errors due to different representation of
floating point numbers. Relaxing the precision of the test would solve
the problem (but I have no idea about the test suite and so do not know
how to implement this).
What I do also not understand why a fix that only o
On Sat, Jan 26, 2019 at 11:17:35PM +0100, Andreas Beckmann wrote:
> I think I now understood what is happening here.
> Both python3 and dicoweb are being installed in the same run.
> At the time python3 gets configured, dicoweb is already unpacked, but
> not yet configured and therefore /etc/dicowe
I just read the README.Debian file and it says the mariadb version in
stretch might conflict with the mailman3-web version.
If that's really the case, might I suggest the backport be fixed to warn
explicitely about this somehow? maybe conflict with that mariadb
version?
A.
--
Software gets slowe
Your message dated Sat, 02 Feb 2019 01:51:07 +
with message-id
and subject line Bug#919818: fixed in test-kitchen 1.23.2-2
has caused the Debian Bug report #919818,
regarding ruby-net-ssh breaks test-kitchen autopkgtest
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 02 Feb 2019 01:50:56 +
with message-id
and subject line Bug#912168: fixed in node-marked-man 0.4.0-1
has caused the Debian Bug report #912168,
regarding node-marked breaks node-marked-man autopkgtest
to be marked as done.
This means that you claim that the problem has
Package: mailman3
Version: 3.2.0-4~bpo9+1
Severity: grave
I'm finding it difficult to use the "domain" feature of Mailman 3. From
what I understand, it allows you to have two distinct mailing lists
named "test" on (say) t...@example.com and t...@example.net.
Here I'm specifically using the featur
Control: tag -1 pending
Hello,
Bug #919818 in test-kitchen reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/ruby-team/test-kitchen/commit/b8125818be7b1a8b2448949
Processing control commands:
> tag -1 pending
Bug #919818 [src:ruby-net-ssh, src:test-kitchen] ruby-net-ssh breaks
test-kitchen autopkgtest
Added tag(s) pending.
--
919818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Package: mailman3-web
Version: 0+20180916-4
Followup-For: Bug #920304
This actually also occurs in buster at the time of writing and should
definitely be fixed in unstable, not just in backports.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'
Package: preload
Version: 0.6.4-3
Followup-For: Bug #920197
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
Hello,
I think this problem is caused by the autoreconf cruft found in the debian/
directory of the package, which causes the package to fail to reautoconf at
Package: mailman3-web
Followup-For: Bug #921128
I have tried to reproduce this in buster and at first I seem to recall
I did reproduce it, but now I somewhat managed to get through and have
it installed correctly.
Also note this might be a bug specific to MySQL: running the dbconfig
stuff with a
Your message dated Sat, 02 Feb 2019 00:05:15 +
with message-id
and subject line Bug#920935: fixed in docker.io 18.09.1+dfsg1-5
has caused the Debian Bug report #920935,
regarding docker.io: ships /usr/bin/containerd-shim, already provided by
containerd
to be marked as done.
This means that y
Package: yum-utils
Severity: grave
Tags: security
This was assigned CVE-2018-10897:
https://bugzilla.redhat.com/show_bug.cgi?id=1600221
https://github.com/rpm-software-management/yum-utils/commit/7554c0133eb830a71dc01846037cc047d0acbc2c
https://github.com/rpm-software-management/yum-utils/commit/6
Processing commands for cont...@bugs.debian.org:
> severity 917408 grave
Bug #917408 [src:jupyter-notebook] jupyter-notebook: CVE-2018-19352
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
917408: https://bugs.debian.org/cg
Your message dated Fri, 01 Feb 2019 23:03:28 +
with message-id
and subject line Bug#919623: fixed in rssh 2.3.4-5+deb9u1
has caused the Debian Bug report #919623,
regarding rssh: CVE-2019-118: Remote code execution in scp support
to be marked as done.
This means that you claim that the pr
Your message dated Fri, 01 Feb 2019 23:03:26 +
with message-id
and subject line Bug#919147: fixed in php-pear
1:1.10.1+submodules+notgz-9+deb9u1
has caused the Debian Bug report #919147,
regarding php-pear: CVE-2018-1000888
to be marked as done.
This means that you claim that the problem has
On Thu, Jan 03, 2019 at 11:06:23PM +0100, Moritz Mühlenhoff wrote:
> On Tue, Aug 01, 2017 at 10:02:39AM -0400, Sean Whitton wrote:
> > Hello Damyan,
> >
> > On Tue, Aug 01, 2017 at 08:58:38AM +, Damyan Ivanov wrote:
> > > When firefox hits unstable (probably towards the end of this year) this
Package: mailman3-web
Version: 0+20180916-2~bpo9+1
Severity: grave
I can't seem to install mailman3-web, at least from backports:
Paramétrage de mailman3-web (0+20180916-2~bpo9+1) ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dbconfig-common: writing config to /etc/
Processing commands for cont...@bugs.debian.org:
> found 773720 14.4.1-5
Bug #773720 {Done: Thorsten Alteholz } [src:sox] sox:
CVE-2014-8145
Marked as found in versions sox/14.4.1-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
773720: https://bugs.debian.org/
package: src:wine-development
severity: serious
version: 3.12-2
This has been fixed in wine [0]. It also needs to be fixed in wine-development.
Best wishes,
Mike
[0] http://bugs.debian.org/918666
Your message dated Fri, 01 Feb 2019 21:49:45 +
with message-id
and subject line Bug#918234: fixed in ruby-asciidoctor-pdf 1.5.0~alpha.17.dev-3
has caused the Debian Bug report #918234,
regarding ruby-asciidoctor-pdf: FTBFS in sid
to be marked as done.
This means that you claim that the proble
Your message dated Fri, 01 Feb 2019 20:38:05 +
with message-id
and subject line Bug#919594: fixed in memkind 1.8.0-2
has caused the Debian Bug report #919594,
regarding memkind: baseline violation on amd64 (and FTBFS everywhere else)
to be marked as done.
This means that you claim that the pr
Package: pbbam
Version: 0.19.0+dfsg-1
Severity: serious
Tags: patch
Justification: autopkgtest failures block migration
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
Dear Afif,
Since the upload of 0.18.0+dfsg-1, pbbam's autopkgtests have been
consistently failing
Hrm, due to lack of tuits I did not manage to get it work _correctly_ with
system jemalloc yet. Thus, I'm uploading a fix for the -mssse4.2 issue;
plus a working testsuite. Porting patches can come later, once the package
is in testing (soft freeze!)
Meow.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Romanes e
Processing commands for cont...@bugs.debian.org:
> severity 920977 serious
Bug #920977 [mercurial-common] Breaks loading of db backends in Trac
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
920977: https://bugs.debian.o
Package: libicu-dev
Followup-For: Bug #920900
Just pointing out that the changelog for the upgrade specifically mentions this
change.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Arc
Your message dated Fri, 01 Feb 2019 18:38:40 +
with message-id
and subject line Bug#921110: Removed package(s) from unstable
has caused the Debian Bug report #830493,
regarding Lacks depends
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not t
Am Samstag, den 26.01.2019, 15:23 +0100 schrieb Bruno Kleinert:
> Hi David,
>
> please consider addressing this RC bug.
>
> Just to raise awareness: I plan to NMU with my previously attached
> patch around week 7.
>
> Cheers - Bruno
Hi,
I uploaded to the DELAYED=10 queue.
Cheers - Bruno
sig
Your message dated Fri, 01 Feb 2019 18:37:34 +
with message-id
and subject line Bug#921098: Removed package(s) from unstable
has caused the Debian Bug report #917485,
regarding ckermit: relax openssl version check or tighten libssl1.x.y
dependencies
to be marked as done.
This means that you
Your message dated Fri, 01 Feb 2019 18:37:34 +
with message-id
and subject line Bug#921098: Removed package(s) from unstable
has caused the Debian Bug report #915992,
regarding ckermit FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 01 Feb 2019 18:37:34 +
with message-id
and subject line Bug#921098: Removed package(s) from unstable
has caused the Debian Bug report #918061,
regarding Should ckermit be removed?
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 01 Feb 2019 18:37:34 +
with message-id
and subject line Bug#921098: Removed package(s) from unstable
has caused the Debian Bug report #847611,
regarding ckermit: Please migrate to openssl1.1 in buster
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 01 Feb 2019 18:35:21 +
with message-id
and subject line Bug#900997: fixed in print-manager 4:18.12.1-2
has caused the Debian Bug report #900997,
regarding [print-manager] sends password to remote cups server
to be marked as done.
This means that you claim that the prob
Your message dated Fri, 01 Feb 2019 18:37:34 +
with message-id
and subject line Bug#921098: Removed package(s) from unstable
has caused the Debian Bug report #905815,
regarding ckermit fails to trap errors from make
to be marked as done.
This means that you claim that the problem has been dea
Package: libdfp
Version: 1.0.13-2
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
Hi Frédéric,
In libdfp 1.0.13-2 you've ported the package to use python3 by default
instead of python (thanks!), but you do not have
Processing commands for cont...@bugs.debian.org:
> reassign 916966 src:linux
Bug #916966 [src:linuxptp] linuxptp FTBFS with glibc 2.28
Bug reassigned from package 'src:linuxptp' to 'src:linux'.
No longer marked as found in versions linuxptp/1.9.2-1.
Ignoring request to alter fixed versions of bug
Package: firmware-amd-graphics
Version: 20190114-1
Severity: critical
Debian: Stretch amd64
Regression: Yes
Graphic card: AMD Radeon Rx 580
Good Evening,
since the latest update of xserver-xorg-video-amdgpu and
firmware-amd-graphics, most GL applications do not display anything and
display
Hi,
Thanks to ping. I'll try it this weekend.
On Tue, 29 Jan 2019 08:26:43 +0900,
Moritz Mühlenhoff wrote:
>
> On Mon, Dec 03, 2018 at 04:19:44PM +, Youhei SASAKI wrote:
> > Control: tag -1 pending
> >
> > Hello,
> >
> > Bug #909933 in jekyll reported by you has been fixed in the
> > Git rep
Your message dated Fri, 01 Feb 2019 16:19:22 +
with message-id
and subject line Bug#915756: fixed in tweepy 3.6.0-1.1
has caused the Debian Bug report #915756,
regarding tweepy FTBFS with python-pip 18.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
It's a problem with opcache
insert /opcache.optimization_level=0xFBFF/ into opcache.ini solves
the problem.
Workaround will be integrated into xdebug2.7.0
Unfortunately the workaround mentioned for arm64 breaks ppc64el arch as
compiling on buster fails with following error - what do we do ?
Thanks
BT check (recess model): prob vs. prob_fv OK
2c2
<
On Fri, 1 Feb 2019 at 14:20, Andreas Tille wrote:
>
> Hi,
>
> I tried to have a look at the issue caused by t-coffee 12 which became
> visible in the smoke test of libbio-tools-run-alignment-tcoffee-perl.
> Liubov had checked it before and filed an issue upstream[1] but at my
> side the test to re
Your message dated Fri, 01 Feb 2019 15:04:10 +
with message-id
and subject line Bug#920835: fixed in mlucas 17.1-3
has caused the Debian Bug report #920835,
regarding mlucas FTBFS on !amd64: test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hi,
since I wanted to track down this issue I tried
t_coffee -aln sproteases_small.cw_aln sproteases_small.muscle
sproteases_small.tc_aln -outfile combined_aln.aln
on my usual testing machine. However, when running on sid I get the
reported error:
*
Control: tags -1 confirmed
Hi Paul,
Paul Wise ezt írta (időpont: 2019. febr. 1., P, 18:39):
>
> Control: found -1 unattended-upgrades/1.10
>
> On Sat, 05 Jan 2019 11:24:42 +0800 Paul Wise wrote:
>
> > I thought this had been fixed but recently I got git upgraded to
> > experimental for some reas
Unfortunately the workaround mentioned for arm64 breaks ppc64el arch as
compiling on buster fails with following error - what do we do ?
Thanks
BT check (recess model): prob vs. prob_fv OK
2c2
< r
On Wed, Jan 02, 2019 at 11:27:10PM +0100, Moritz Muehlenhoff wrote:
> Package: ckermit
> Severity: serious
>
> Should ckermit be removed from the archive?
> - Hasn't seen a maintainer upload in almost six years
> - Multiple RC bugs at this point
No objections for a month, I've now filed a removal
Processing control commands:
> tags -1 confirmed
Bug #905877 [unattended-upgrades] regression in 1.4: upgrades random packages
from testing to experimental (doesn't respect pinning?)
Ignoring request to alter tags of bug #905877 to the same tags previously set
--
905877: https://bugs.debian.org
Hi,
I tried to have a look at the issue caused by t-coffee 12 which became
visible in the smoke test of libbio-tools-run-alignment-tcoffee-perl.
Liubov had checked it before and filed an issue upstream[1] but at my
side the test to reproduce the bug does not fail. I wonder if someone
from the Per
Package: gajim
Version: 1.1.2-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After upgrading to gajim 1.1.2, I received a traceback when starting
gajim. Gajim started, but was unable to connect to any servers.
The problem went away with this change:
--- /usr/lib/pyth
Your message dated Fri, 1 Feb 2019 14:33:30 +0100
with message-id <3c35f7a9-a5ba-71fa-579b-5f0dc377f...@debian.org>
and subject line Re: plexmediaserver: 100% cpu usage
has caused the Debian Bug report #921070,
regarding plexmediaserver: 100% cpu usage
to be marked as done.
This means that you cla
Hi victor, you didnt noted tha i mentiones that i use buster, and i
mention that only happened when kamailio need to comunicate
internally.. this means with many modules enables and asterisk in the
game... and i noted that build from upstream already happened in 5.1
and 5.2 so seems its a kamailio
Processing commands for cont...@bugs.debian.org:
> unarchive 773720
Bug #773720 {Done: Thorsten Alteholz } [src:sox] sox:
CVE-2014-8145
Unarchived Bug 773720
> notfixed 773720 14.4.1-5
Bug #773720 {Done: Thorsten Alteholz } [src:sox] sox:
CVE-2014-8145
No longer marked as fixed in versions sox/1
Your message dated Fri, 01 Feb 2019 13:05:14 +
with message-id
and subject line Bug#742347: fixed in node-cssstyle 0.2.14-2
has caused the Debian Bug report #742347,
regarding node-jsdom: require("jsdom") does not work in nodejs: missing
cssstyle module
to be marked as done.
This means that
severity 921015 normal
--
thanks
Hello,
*You didn't mentioned if you are using systemd or sysv. Both have rules to
create and set permissions for /var/run/kamailio dir:*
*# debian/kamailio.init*
*HOMEDIR=/var/run/$NAME[..]USER=kamailioGROUP=kamailio[..]*
*# /var/run can be a tmpfsif [ ! -d
Your message dated Fri, 01 Feb 2019 12:39:07 +
with message-id
and subject line Bug#921057: fixed in unanimity 3.3.0+dfsg-2
has caused the Debian Bug report #921057,
regarding unanimity: don't depend on build target
to be marked as done.
This means that you claim that the problem has been dea
Control: found -1 unattended-upgrades/1.10
On Sat, 05 Jan 2019 11:24:42 +0800 Paul Wise wrote:
> I thought this had been fixed but recently I got git upgraded to
> experimental for some reason. I've included the full debug log below.
This happened again with 1.10. I can add the log if needed. I'
Processing control commands:
> found -1 unattended-upgrades/1.10
Bug #905877 [unattended-upgrades] regression in 1.4: upgrades random packages
from testing to experimental (doesn't respect pinning?)
Marked as found in versions unattended-upgrades/1.10.
--
905877: https://bugs.debian.org/cgi-bin
Control: reassign -1 node-cssstyle
node-jsdom debian/control has a node-cssstyle dependency. However a
simple test shows that cssstyle is unusable:
$ node -e 'require("cssstyle")'
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module 'cssom'
at Function.Module._re
Control: tag -1 pending
Hello,
Bug #920935 in docker.io reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/docker-team/docker/commit/ce14a47751a90a86ff02749ece5e1f
Processing control commands:
> reassign -1 node-cssstyle
Bug #742347 [node-jsdom] node-jsdom: require("jsdom") does not work in nodejs:
missing cssstyle module
Bug reassigned from package 'node-jsdom' to 'node-cssstyle'.
No longer marked as found in versions node-jsdom/0.8.10+dfsg1-1.
Ignoring re
Processing control commands:
> tag -1 pending
Bug #920935 [docker.io] docker.io: ships /usr/bin/containerd-shim, already
provided by containerd
Added tag(s) pending.
--
920935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Hello,
meanwhile I found the bug and I will upload a fixed Version 5.3.1 soon.
Regards
Bernd
-Original Message-
From: Santiago Vila [mailto:sanv...@debian.org]
Sent: Freitag, 1. Februar 2019 00:41
To: Debian BTS
Subject: Bug#921041: shellia: FTBFS (failing tests)
Package: src:shellia
El dj. 31 de 01 de 2019 a les 20:06 +, en/na Matthew Hall va
escriure:
> No problem!
>
> It seems to actually be a known issue(?) with SOGo upstream, I’ve
> managed to open a bug report on there own tracker:
>
> https://sogo.nu/bugs/view.php?id=4659
>
> Looks like at least one other punter i
Processing commands for cont...@bugs.debian.org:
> found 920577 2.6~RC+dfsg-2
Bug #920577 [ocsinventory-server] ocsinventory-server: depends on no longer
available libjs-select2.js
Ignoring request to alter found versions of bug #920577 to the same values
previously set
> thanks
Stopping process
Processing commands for cont...@bugs.debian.org:
> notfound 920577 2.5+dfsg-1
Bug #920577 [ocsinventory-server] ocsinventory-server: depends on no longer
available libjs-select2.js
Ignoring request to alter found versions of bug #920577 to the same values
previously set
> thanks
Stopping process
Your message dated Fri, 01 Feb 2019 10:05:01 +
with message-id
and subject line Bug#918149: fixed in terminator 1.91-3
has caused the Debian Bug report #918149,
regarding terminator: Unstated Dependency On `dbus-x11`
to be marked as done.
This means that you claim that the problem has been de
Processing commands for cont...@bugs.debian.org:
> # add back fixed version from stretch-security upload
> fixed 921039 2.7.13-2+deb9u3
Bug #921039 [python2.7] CVE-2018-14647
Marked as fixed in versions python2.7/2.7.13-2+deb9u3.
> thanks
Stopping processing here.
Please contact me if you need as
Processing commands for cont...@bugs.debian.org:
> # add back fixed version from stretch-security upload
> fixed 921039 2.7.13-2+deb9u3
Bug #921039 [python2.7] CVE-2018-14647
Ignoring request to alter fixed versions of bug #921039 to the same values
previously set
> thanks
Stopping processing her
Control: reopen -1
Control: found -1 2.7.15-6
Hi
On Fri, Feb 01, 2019 at 08:51:07AM +, Debian Bug Tracking System wrote:
> - CVE-2018-14647: _elementtree.c doesn't call XML_SetHashSalt().
>Closes: #921039.
The change
https://github.com/python/cpython/commit/18b20bad75b4ff0486940f
Processing control commands:
> reopen -1
Bug #921039 {Done: Matthias Klose } [python2.7] CVE-2018-14647
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions p
Package: plexmediaserver
Version: 1.14.1.5488-cc260c476
Severity: critical
Justification: breaks the whole system
Since upgrading plex from 1.13.9.5456-ecd600442 to
1.14.1.5488-cc260c476, my cpu is always pegged at 100%
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debu
On 01.02.19 10:03, Emmanuel Bourg wrote:
> Le 01/02/2019 à 09:17, Per Lundberg a écrit :
>
>> I think that risk is significant. If we go that route, I would suggest a
>> postinst/debhelper message saying that "OpenJDK 8 is included but
>> unsupported. Many packages will not work with it. Use at
Your message dated Fri, 01 Feb 2019 09:19:11 +
with message-id
and subject line Bug#905222: fixed in spambayes 1.1b1+git20190201.1335ca8-1
has caused the Debian Bug report #905222,
regarding spambayes: several binaries fail to run: ImportError: cannot import
name asyncore
to be marked as done
Le 01/02/2019 à 09:17, Per Lundberg a écrit :
> I think that risk is significant. If we go that route, I would suggest a
> postinst/debhelper message saying that "OpenJDK 8 is included but
> unsupported. Many packages will not work with it. Use at your own risk."
> or something similar.
This i
Package: libstdc++-8-dev
Version: 8.2.0-15
Severity: critical
Justification: breaks unrelated software
This problem as arisen during an upgrade. The system is now reporting:
root@redhorse:/tmp# dpkg --configure -a
dpkg: dependency problems prevent configuration of g++-8:
Processing control commands:
> tag -1 pending
Bug #905222 [spambayes] spambayes: several binaries fail to run: ImportError:
cannot import name asyncore
Added tag(s) pending.
--
905222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905222
Debian Bug Tracking System
Contact ow...@bugs.debian.
Control: tag -1 pending
Hello,
Bug #905222 in spambayes reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/python-team/applications/spambayes/commit/da6655f931a97a
Changed-By: Matthias Klose
Closes: 921039 921040
Changes:
python2.7 (2.7.15-6) unstable; urgency=medium
.
* Update to 20190201 from the 2.7 branch.
- CVE-2013-1752: Limit imaplib.IMAP4_SSL.readline().
- CVE-2018-14647: _elementtree.c doesn't call XML_SetHashSalt().
C
On 1/29/19 3:36 PM, Markus Koschany wrote:
> We usually ship only with one JDK per release because of security
> support. OpenJDK 8 will be EOL before the end of the Debian 10 release
> cycle. We still have a couple of packages that will not compile with
> OpenJDK 11 hence we also thought about sh
Processing commands for cont...@bugs.debian.org:
> fixed 921039 2.7.13-2+deb9u3
Bug #921039 [python2.7] CVE-2018-14647
Marked as fixed in versions python2.7/2.7.13-2+deb9u3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921039: https://bugs.debian.org/cgi-bin/bu
81 matches
Mail list logo
