host's instance of systemd; the package build runs in a
chroot, but in the same process namespace.
There is currently no way to get Launchpad to run ordinary package
builds in a container booted with systemd; no Build-Depends or
environment variables or anything else will help
Recommends seems like the right thing to use for an optional feature -
but python3-dnspython already Recommends: python3-httpx, and that's
where the code that's directly using the httpx library lives. So I
wonder if it really makes sense to change dnsdiag for this? A
Recommends there rather than
Colin Watson pushed new tag debian/1.11.3+dfsg-1 at Debian Python Team /
packages / python-avro
--
View it on GitLab:
https://salsa.debian.org/python-team/packages/python-avro/-/tree/debian/1.11.3+dfsg-1
You're receiving this email because of your account on salsa.debian.org
Colin Watson pushed to branch master at Debian Python Team / packages /
python-avro
Commits:
bb677a3c by Colin Watson at 2024-04-30T18:10:06+01:00
releasing package python-avro version 1.11.3+dfsg-1
- - - - -
1 changed file:
- debian/changelog
Changes
Colin Watson pushed to branch upstream at Debian Python Team / packages /
python-avro
Commits:
7454f2c3 by Colin Watson at 2024-04-30T18:03:11+01:00
New upstream version 1.11.3+dfsg
- - - - -
30 changed files:
- .github/dependabot.yml
- .github/workflows/codeql-csharp-analysis.yml
Colin Watson pushed new tag upstream/1.11.3+dfsg at Debian Python Team /
packages / python-avro
--
View it on GitLab:
https://salsa.debian.org/python-team/packages/python-avro/-/tree/upstream/1.11.3+dfsg
You're receiving this email because of your account on salsa.debian.org
Colin Watson pushed to branch master at Debian Python Team / packages /
python-avro
Commits:
8e73f2ce by Colin Watson at 2024-04-30T18:03:04+01:00
d/copyright: Add lang/rust/* to Files-Excluded
We exclude all other non-Python language bindings; not excluding the
Rust bindings looks like
Colin Watson pushed to branch pristine-tar at Debian Python Team / packages /
python-avro
Commits:
c70ab2de by Colin Watson at 2024-04-30T18:03:12+01:00
pristine-tar data for python-avro_1.11.3+dfsg.orig.tar.xz
- - - - -
2 changed files:
- + python-avro_1.11.3+dfsg.orig.tar.xz.delta
//git.savannah.gnu.org/cgit/groff.git/commit/?id=0815e503dba8d5c05921d68c6c718fe8f8440ee8.
I'll also fix it in Debian.
--
Colin Watson (he/him) [cjwat...@debian.org]
cjwatson pushed a commit to branch master
in repository groff.
commit 0815e503dba8d5c05921d68c6c718fe8f8440ee8
Author: Colin Watson
AuthorDate: Tue Apr 30 12:06:31 2024 +0100
[gropdf] Fix date format.
Commit d7bbfb04ea25a82a8597cdef6ebb391cb78ab47c caused gropdf to emit
invalid
rate bug - I don't maintain the
dropbear packages.
--
Colin Watson (he/him) [cjwat...@debian.org]
rate bug - I don't maintain the
dropbear packages.
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #1069756 in readability 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:
eam intends to switch to bleach; I think we can
just patch setup.py in Debian in the meantime though. I'll do that.
--
Colin Watson (he/him) [cjwat...@debian.org]
eam intends to switch to bleach; I think we can
just patch setup.py in Debian in the meantime though. I'll do that.
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: tag -1 pending
Hello,
Bug #1069608 in topplot 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:
Control: tag -1 pending
Hello,
Bug #1069360 in python-cytoolz 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:
Control: tag -1 pending
Hello,
Bug #1069818 in toolz 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:
ishDoughnutE
I sent a patch for this upstream as
https://github.com/gyoto/Gyoto/pull/17. Here's a patch to fix the
Debian package in the meantime.
--
Colin Watson (he/him) [cjwat...@debian.org]
>From 19e6f4bcdc33cbd7995027bf56ec3b5a7125ea5f Mon Sep 17 00:00:00 2001
ishDoughnutE
I sent a patch for this upstream as
https://github.com/gyoto/Gyoto/pull/17. Here's a patch to fix the
Debian package in the meantime.
--
Colin Watson (he/him) [cjwat...@debian.org]
>From 19e6f4bcdc33cbd7995027bf56ec3b5a7125ea5f Mon Sep 17 00:00:00 2001
n/rules:8: binary-arch] Error 25
I've proposed
https://salsa.debian.org/science-team/pyferret/-/merge_requests/3 to fix
this.
--
Colin Watson (he/him) [cjwat...@debian.org]
n/rules:8: binary-arch] Error 25
I've proposed
https://salsa.debian.org/science-team/pyferret/-/merge_requests/3 to fix
this.
--
Colin Watson (he/him) [cjwat...@debian.org]
places to look, or things I might be able to tweak to make
the bug more reliably reproducible (e.g. places to insert artificial
delays).
I remain entirely unable to reproduce this bug in any form on my laptop.
--
Colin Watson (he/him) [cjwat...@debian.org]
a drop-in config
> fragment in some ssh.service.d/ directory. But this, and other similar
> synchronization targets, exist so that one does not necessarily need
> to know about every other service running on the system.
This sounds like a reasonable proposal to me. I'm just CCing Debian's
systemd mai
a drop-in config
> fragment in some ssh.service.d/ directory. But this, and other similar
> synchronization targets, exist so that one does not necessarily need
> to know about every other service running on the system.
This sounds like a reasonable proposal to me. I'm just CCing Debian's
systemd mai
a drop-in config
> fragment in some ssh.service.d/ directory. But this, and other similar
> synchronization targets, exist so that one does not necessarily need
> to know about every other service running on the system.
This sounds like a reasonable proposal to me. I'm just CCing Debian's
systemd mai
On Thu, Apr 18, 2024 at 12:56:06PM +0200, Jérémy Lal wrote:
> Le jeu. 18 avr. 2024 à 12:29, Colin Watson a écrit :
> Ok, and sorry, I got frustrated by the "1 column space on the right" change
> of
> https://gitlab.com/man-db/man-db/-/merge_requests/11
[...]
> Indeed, the
1) The man-db Debian maintainer is the same person as the upstream
maintainer, i.e. me.
2) The Debian packaging does not contain any changes to how MANWIDTH is
handled.
What are you talking about?
--
Colin Watson (he/him) [cjwat...@debian.org]
On Thu, Apr 04, 2024 at 10:47:29PM -0500, Dave Kemper wrote:
> On Sun, Mar 31, 2024 at 5:31 AM Colin Watson wrote:
> > I've omitted README.git to ensure that we still warn people who don't
> > know what they're doing that running "./bootstrap" may not be the right
> &g
t wasn't just being abused as free mass
storage in general, it was very very dodgy stuff that required urgent
takedown enforcement. We talked IS down from making it require a login
to use the service at all and this was the compromise.
--
Colin Watson (he/him) [cjwat.
$ remove-package -s noble -a armhf -b -m 'Broken with 64-bit time_t on armhf;
see bug 2061476' nfs-ganesha nfs-ganesha-gpfs nfs-ganesha-mem
nfs-ganesha-nullfs nfs-ganesha-proxy-v4 nfs-ganesha-vfs
Removing packages from noble:
nfs-ganesha 4.3-8 in noble armhf
nfs-ganesha-gpfs
Control: tag -1 pending
Hello,
Bug #1068349 in nbconvert 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:
Control: tag -1 pending
Hello,
Bug #1042699 in nbconvert 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:
On Thu, Apr 11, 2024 at 01:27:54PM -0500, G. Branden Robinson wrote:
> At 2024-04-11T15:37:46+0100, Colin Watson wrote:
> > On Thu, Apr 11, 2024 at 10:26:55AM -0400, Theodore Ts'o wrote:
> > > Or, because some upstream maintainers have learned through, long,
> > > b
nfigure script to be busted (sometimmes subtly), and
> so distrust relying on blind autoreconf always working.
When was the last time this actually happened to you? I certainly
remember it being a problem in the early 2.5x days, but it's been well
over a decade since this
Colin Watson has proposed merging ~cjwatson/lp-archive:typos into
lp-archive:main.
Commit message:
Fix a couple of typos in the landing page
Requested reviews:
Launchpad code reviewers (launchpad-reviewers)
For more details, see:
https://code.launchpad.net/~cjwatson/lp-archive/+git/lp
st so that its other facilities can still be
useful without getting in my way. Search for "compat_release" in
https://salsa.debian.org/janitor-team/janitor.debian.net/-/blob/master/k8s/policy.conf.
--
Colin Watson (he/him) [cjwat...@debian.org]
libpam-modules | grep --count
^libpam-
68
$ apt-file search security/pam_ | grep -v libpam-modules | grep --count ^pam-
1
And the Debian PAM mini-policy says:
1) Packages should use the naming scheme of `libpam-' (eg.
libpam-ldap).
--
Colin Watson (he/him) [cjwat...@debian.org]
libpam-modules | grep --count
^libpam-
68
$ apt-file search security/pam_ | grep -v libpam-modules | grep --count ^pam-
1
And the Debian PAM mini-policy says:
1) Packages should use the naming scheme of `libpam-' (eg.
libpam-ldap).
--
Colin Watson (he/him) [cjwat...@debian.org]
On Sat, Apr 06, 2024 at 06:32:47PM +0200, Bastian Germann wrote:
> Am 06.04.24 um 18:29 schrieb Colin Watson:
> > There might be some small errors in this, but I couldn't see any when
> > eyeballing the resulting uniquified list of Maintainer fields. It looks
> > like 7
> connected
> Failed to retrieve unit state: Transport endpoint is not connected
> ...
> ```
>
> And this process is very time-consuming also.
Hi,
This is all fairly clearly a systemd issue rather than anything
specifically to do with man-db, so reassigning there. I'm afraid I
don't have any further clues though.
--
Colin Watson (he/him) [cjwat...@debian.org]
> connected
> Failed to retrieve unit state: Transport endpoint is not connected
> ...
> ```
>
> And this process is very time-consuming also.
Hi,
This is all fairly clearly a systemd issue rather than anything
specifically to do with man-db, so reassigning there. I'm afraid I
don't have any further clues though.
--
Colin Watson (he/him) [cjwat...@debian.org]
gue that this, and the similar error case in patches-unapplied, is
symmetric with the error case in the patches-applied workflow (although
it's true that there is redundancy in _commits_ in the latter case).
--
Colin Watson (he/him) [cjwat...@debian.org]
t's https://bugs.debian.org/1068311 which I linked to elsewhere
in this thread.
--
Colin Watson (he/him) [cjwat...@debian.org]
t's https://bugs.debian.org/1068311 which I linked to elsewhere
in this thread.
--
Colin Watson (he/him) [cjwat...@debian.org]
e expressed in gnulib-cache.m4.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
s
between packages. But maybe.
--
Colin Watson (he/him) [cjwat...@debian.org]
s
between packages. But maybe.
--
Colin Watson (he/him) [cjwat...@debian.org]
hat would still mean one more library
than strictly needed (once the GSS-API stuff is split out), but at least
it would be one small library rather than a big linkage chain over 30
times the size. I could probably justify keeping it in that case.
--
Colin Watson (he/him) [cjwat...@debian.org]
hat would still mean one more library
than strictly needed (once the GSS-API stuff is split out), but at least
it would be one small library rather than a big linkage chain over 30
times the size. I could probably justify keeping it in that case.
--
Colin Watson (he/him) [cjwat...@debian.org]
On Wed, Apr 03, 2024 at 02:55:08PM +0200, Marco d'Itri wrote:
> On Apr 03, Colin Watson wrote:
> > I wondered if anything could be done to avoid this or refactor it
> > somehow?
> Sure: I think that it makes sense to just disable NETGROUP (which is
> the conditional for
(via /run/systemd/system)
LSM: AppArmor: enabled
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
, but configure fails to detect this).
-- Colin Watson Wed, 03 Apr 2024 12:06:08 +0100
--
Colin Watson (he/him) [cjwat...@debian.org]
On Tue, Apr 02, 2024 at 08:20:31PM +0300, Adrian Bunk wrote:
> On Tue, Apr 02, 2024 at 06:05:22PM +0100, Colin Watson wrote:
> > On Tue, Apr 02, 2024 at 06:57:20PM +0300, Adrian Bunk wrote:
> > > Does gnulib upstream support upgrading/downgrading the gnulib m4 files
> &
-local-dir
option of gnulib-tool, which allows overriding individual Gnulib files
or modules or applying patches to Gnulib files; or you can define a
bootstrap_post_import_hook function in bootstrap.conf and do whatever
you want there.
--
Colin Watson (he/him) [cjwat...@debian.org]
point out that
DNS-based ACLs are supported by Match blocks without needing a separate
library.
--
Colin Watson (he/him) [cjwat...@debian.org]
point out that
DNS-based ACLs are supported by Match blocks without needing a separate
library.
--
Colin Watson (he/him) [cjwat...@debian.org]
On Tue, Apr 02, 2024 at 12:04:26PM +0200, Marco d'Itri wrote:
> On Apr 02, Colin Watson wrote:
> > At the time, denyhosts was popular, but it was removed from Debian
> > several years ago. I remember that, when I dealt with that on my own
> > systems, fail2ban seemed like th
On Tue, Apr 02, 2024 at 12:04:26PM +0200, Marco d'Itri wrote:
> On Apr 02, Colin Watson wrote:
> > At the time, denyhosts was popular, but it was removed from Debian
> > several years ago. I remember that, when I dealt with that on my own
> > systems, fail2ban seemed like th
I haven't tested it. I think we should at least roughly coordinate this
so that there isn't a long period when testing users have no last login
information at all, though, so let me know when you'd like me to do
that.
It might be a good idea to wait until the main bulk of the 64-bit time_t
tran
On Tue, Apr 02, 2024 at 10:58:01AM +0200, Chris Hofstaedtler wrote:
> I'll note that #1068017 has discussion about enabling
> pam_lastlog2.so, where we'd also appreciate your input regarding
> sshd, Colin.
Yep, replied there.
--
Colin Watson (he/him)
I haven't tested it. I think we should at least roughly coordinate this
so that there isn't a long period when testing users have no last login
information at all, though, so let me know when you'd like me to do
that.
It might be a good idea to wait until the main bulk of the 64-bit time_t
tran
ler
and I think safer to just have a separate openssh-client-gsskeyex
package. Like today's openssh-client, it would be usable both with and
without GSS-API key exchange.
--
Colin Watson (he/him) [cjwat...@debian.org]
ler
and I think safer to just have a separate openssh-client-gsskeyex
package. Like today's openssh-client, it would be usable both with and
without GSS-API key exchange.
--
Colin Watson (he/him) [cjwat...@debian.org]
wayscurious/112192949171400643), so maybe
it would be an option to drop --with-selinux in favour of that? I've
never used SELinux, so I'd need an expert to weigh on here.
Comments welcome,
--
Colin Watson (he/him) [cjwat...@debian.org]
wayscurious/112192949171400643), so maybe
it would be an option to drop --with-selinux in favour of that? I've
never used SELinux, so I'd need an expert to weigh on here.
Comments welcome,
--
Colin Watson (he/him) [cjwat...@debian.org]
On Mon, Apr 01, 2024 at 05:24:45PM +0200, Simon Josefsson wrote:
> Colin Watson writes:
> > On Mon, Apr 01, 2024 at 11:33:06AM +0200, Simon Josefsson wrote:
> >> Running ./bootstrap in a tarball may lead to different results than the
> >> maintainer running
or git.
>
> Er, well, there goes every C package for which I'm upstream, all of which
> have M4 macros in m4/* that do not come from an external source.
Ditto. And a bunch of the packages where I'm not upstream too, such as
that famously enthusiastic adopter of all things GNU, Open
If you're faced with a user report containing translated messages,
then it's much easier to figure out what's going on if you can just
look for them in git. I've found this to be a source of frustration
on several occasions when dealing with packages where ./boots
g for a new distro
patch to OpenSSH!
I'd be happy to include this if upstream does, but I don't think I'm
likely to apply this in advance of upstream.
--
Colin Watson (he/him) [cjwat...@debian.org]
g for a new distro
patch to OpenSSH!
I'd be happy to include this if upstream does, but I don't think I'm
likely to apply this in advance of upstream.
--
Colin Watson (he/him) [cjwat...@debian.org]
On Sun, Mar 31, 2024 at 06:04:47AM -0500, G. Branden Robinson wrote:
> At 2024-03-31T11:30:25+0100, Colin Watson wrote:
> > I looked into what it would take for Debian's groff package to do a
> > full rebootstrap from its packaged version of gnulib. It seems
> > relat
cjwatson pushed a commit to branch master
in repository groff.
commit 822fef56e9ab7cbe69337b045f6f20e32e25f566
Author: Colin Watson
AuthorDate: Sun Mar 31 11:29:14 2024 +0100
Distribute bootstrap and bootstrap.conf
With the recent xz-utils backdoor, there's been more focus on cases
is very low - IME it's much more common in such cases to
either rename the macro file to be obviously project-specific or to find
some workaround that doesn't require changing the upstream macro - but
I've never seen anything resembling a robust analysis of this and I may
well have a skewed vie
On Sun, Mar 31, 2024 at 09:35:09AM +0200, Bastian Blank wrote:
> On Sat, Mar 30, 2024 at 08:15:10PM +0000, Colin Watson wrote:
> > On Sat, Mar 30, 2024 at 05:12:17PM +0100, Sirius wrote:
> > > I have seen discussion about shifting away from the whole auto(re)conf
> > >
With the recent xz-utils backdoor, there's been more focus on cases
where build systems rely on files produced by "make dist" and included
in release tarballs. It's already fairly standard practice for
distributions to rebuild configure scripts using autoreconf, but less so
to rebuild the files
using it, but it did make it into
noble-proposed (the current unstable analogue) for some time and noble
(the current testing analogue) briefly.
--
Colin Watson (he/him) [cjwat...@debian.org]
*** This bug is a duplicate of bug 1922130 ***
https://bugs.launchpad.net/bugs/1922130
** This bug has been marked a duplicate of bug 1922130
Request addition of Fedora / Redhat "sftp-force-permissions" patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1922130 ***
https://bugs.launchpad.net/bugs/1922130
** This bug has been marked a duplicate of bug 1922130
Request addition of Fedora / Redhat "sftp-force-permissions" patch
--
You received this bug notification because you are a member of Ubuntu
Touch
to be
doing some testing of that soon.
There's also work on the libsystemd side to load decompression libraries
only when actually needed, which they wouldn't be in this case.
--
Colin Watson (he/him) [cjwat...@debian.org]
what the Debian pam maintainers intend to do about it, but
this is surely the result of:
https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816
A note in NEWS.Debian might be worthwhile.
--
Colin Watson (he/him) [cjwat...@debian.org]
something that Debian can unilaterally change. And
in a number of cases switching build system would be pretty non-trivial.
--
Colin Watson (he/him) [cjwat...@debian.org]
have
upstream commit access. This event is traditionally followed by
cursing.
--
Colin Watson (he/him) [cjwat...@debian.org]
Control: reopen -1
On Thu, Mar 28, 2024 at 04:12:19PM +0100, Sebastian Ramacher wrote:
> On 2024-03-28 13:46:14 +0000, Colin Watson wrote:
> > Package: release.debian.org
> > Severity: normal
> > X-Debbugs-Cc: memcac...@packages.debian.org
> > Control: affects
Control: reopen -1
On Thu, Mar 28, 2024 at 04:12:19PM +0100, Sebastian Ramacher wrote:
> On 2024-03-28 13:46:14 +0000, Colin Watson wrote:
> > Package: release.debian.org
> > Severity: normal
> > X-Debbugs-Cc: memcac...@packages.debian.org
> > Control: affects
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: memcac...@packages.debian.org
Control: affects -1 + src:memcached
User: release.debian@packages.debian.org
Usertags: binnmu
nmu memcached_1.6.23-1 . armel armhf . unstable . -m "Rebuild for time_t"
--
Colin Wats
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: memcac...@packages.debian.org
Control: affects -1 + src:memcached
User: release.debian@packages.debian.org
Usertags: binnmu
nmu memcached_1.6.23-1 . armel armhf . unstable . -m "Rebuild for time_t"
--
Colin Wats
Control: tag -1 pending
Hello,
Bug #1064761 in libsdl-perl 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:
This uses faketime, so I would bet that it's pointing out issues there
similar to bug 2059037 / bug 2059078.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059274
Title:
dgit time_t regression
To
On Sat, Mar 23, 2024 at 01:49:19AM +, Thorsten Glaser wrote:
> Colin Watson dixit:
> >Could you try the somewhat further reduced patch in
>
> The package made from that branch built fine in my cowbuilder,
> and I have all reason to assume it’ll do so in sbuild/buildd.
Than
On Sat, Mar 23, 2024 at 01:49:19AM +, Thorsten Glaser wrote:
> Colin Watson dixit:
> >Could you try the somewhat further reduced patch in
>
> The package made from that branch built fine in my cowbuilder,
> and I have all reason to assume it’ll do so in sbuild/buildd.
Than
On Thu, Mar 21, 2024 at 10:35:17PM +, Thorsten Glaser wrote:
> Colin Watson dixit:
> >Could you try the somewhat further reduced patch in
>
> I’ve started a build and will let you know probably when I get
> back late tomorrow.
Thanks! No rush - I won't be at a proper com
On Thu, Mar 21, 2024 at 10:35:17PM +, Thorsten Glaser wrote:
> Colin Watson dixit:
> >Could you try the somewhat further reduced patch in
>
> I’ve started a build and will let you know probably when I get
> back late tomorrow.
Thanks! No rush - I won't be at a proper com
ixed release
> (14 probably).
This configure check doesn't use the usual autoconf result caching
arrangements, which makes it a bit more awkward to override from
debian/rules. There are options, but an extended configure check that I
could send upstream would probably be best.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
ixed release
> (14 probably).
This configure check doesn't use the usual autoconf result caching
arrangements, which makes it a bit more awkward to override from
debian/rules. There are options, but an extended configure check that I
could send upstream would probably be best.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
in
this bug, "apt-get indextargets" omits the Release file.
For now, I'll probably dodge the problem by requiring the user to
specify which architectures they want, and then I don't need the Release
file. But I feel like I'm missing something.
Thanks,
--
Colin Watson (he/him)
awkward dependency in a Python codebase due to its
tight coupling with apt, and python-debian is much more convenient in
those terms.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
--
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-python
awkward dependency in a Python codebase due to its
tight coupling with apt, and python-debian is much more convenient in
those terms.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
library quite heavily in tests,
and so we'd need a replacement; the thing to use seems to be respx.
However, debusine needs to run on bookworm. Would you consider
maintaining a backport in bookworm-backports?
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
just the armel/armhf binaries here and
let the others proceed.
Thanks,
--
Colin Watson (he/him) [cjwat...@debian.org]
1 - 100 of 75215 matches
Mail list logo
