Your message dated Thu, 14 Sep 2023 06:21:05 +
with message-id
and subject line Bug#1051885: fixed in kdevelop 4:22.12.2-3
has caused the Debian Bug report #1051885,
regarding kdevelop: FTBFS with llvm-toolchain-16 as default
to be marked as done.
This means that you claim that the problem ha
Processing commands for cont...@bugs.debian.org:
> retitle 1051864 sparse: FTBFS with llvm-toolchain-16 as default
Bug #1051864 [src:sparse] sparce: FTBFS with llvm-toolchain-16 as default
Changed Bug title to 'sparse: FTBFS with llvm-toolchain-16 as default' from
'sparce: FTBFS with llvm-toolcha
Processing commands for cont...@bugs.debian.org:
> retitle 1051863 ldc: FTBFS with llvm-toolchain-16 as default
Bug #1051863 [src:ldc] ldc: FRBFS with llvm-toolchain-16 as default
Changed Bug title to 'ldc: FTBFS with llvm-toolchain-16 as default' from 'ldc:
FRBFS with llvm-toolchain-16 as defaul
Processing control commands:
> reopen -1
Bug #1051819 {Done: Nicholas D Steeves } [fluidsynth]
fluidsynth: Consider building with pipewire support
'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 reop
Source: ring
Version: 20230206.0~ds2-1.3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
ring fails to build from source. From my build log on amd64:
| /bin/bash ../libtool --tag=CXX --mode=compile g++ -std=gnu++17
Your message dated Thu, 14 Sep 2023 05:00:10 +
with message-id
and subject line Bug#1051249: fixed in linux 6.5.3-1
has caused the Debian Bug report #1051249,
regarding linux: s390x: FTBFS: kernel-wedge install-files: missing modules
mptfc, mptsas and mptspi
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> tags 1051889 + upstream
Bug #1051889 [src:freeimage] freeimage: CVE-2020-22524
Added tag(s) upstream.
> forwarded 1051889 https://sourceforge.net/p/freeimage/bugs/319/
Bug #1051889 [src:freeimage] freeimage: CVE-2020-22524
Set Bug forwarded-to-add
Processing commands for cont...@bugs.debian.org:
> tags 1051822 patch
Bug #1051822 [chrony] installed chrony package post-installation script
subprocess returned error exit status 1
Added tag(s) patch.
> stop
Stopping processing here.
Please contact me if you need assistance.
--
1051822: https:
On Wed, 2023-09-13 15:15:10 +0200, Vincent Blut wrote:
> Control: tags -1 + moreinfo
>
> Hi Anibal,
>
> Le 2023-09-13 13:52, Anibal Monsalve Salazar a écrit :
>> Package: chrony
>> Version: 4.2-2
>> Severity: critical
>>
>> # dpkg -i /mnt/apt/archives/chrony_4.4-1_i386.deb
>> (Reading database .
Processing commands for cont...@bugs.debian.org:
> tags 1051885 + pending
Bug #1051885 [src:kdevelop] kdevelop: FTBFS with llvm-toolchain-16 as default
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1051885: https://bugs.debian.org/cgi-bin/b
Your message dated Thu, 14 Sep 2023 03:33:59 +
with message-id
and subject line Bug#1051355: fixed in chromium 117.0.5938.62-1
has caused the Debian Bug report #1051355,
regarding chromium: Crash with seqfault when starting
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 14 Sep 2023 03:33:59 +
with message-id
and subject line Bug#1051355: fixed in chromium 117.0.5938.62-1
has caused the Debian Bug report #1051355,
regarding chromium: Segmentation fault
to be marked as done.
This means that you claim that the problem has been dealt with
I ran more tests, and could reproduce what I think is the same bug without
relying on WINE.
Trying to play an audio file using mpv:i386 [1] on an amd64 host causes a
segfault. While mpv:amd64 has no issue.
[1]: https://packages.debian.org/sid/mpv
I think the problem might actually be related
Processing commands for cont...@bugs.debian.org:
> retitle 1051901 libasound2: 1.2.10 breaks ability to play audio using i386
> binaries on amd64 host
Bug #1051901 [libasound2] 1.2.10 breaks ability to play audio using i386
binaries on amd64 host
Changed Bug title to 'libasound2: 1.2.10 breaks a
Processing commands for cont...@bugs.debian.org:
> retitle 1051901 1.2.10 breaks ability to play audio using i386 binaries on
> amd64 host
Bug #1051901 [libasound2] libasound2: 1.2.10 breaks ability to run i386 WINE on
an amd64 host
Changed Bug title to '1.2.10 breaks ability to play audio using
On 9/12/23 03:01, Paolo Greppi wrote:
This may well be a doxygen bug, can anybody tell if there is any pattern?
I believe this is a deliberate behavior change in Doxygen 1.9.7, made to
address a problem affecting a different doxygen-to-RST converter:
https://github.com/doxygen/doxygen/pull
Processing commands for cont...@bugs.debian.org:
> retitle 1051900 ohcount: aborts with segfault or bus error 90% of the time on
> arm64
Bug #1051900 [ohcount] ohcount: aborts with segfaul or bus error 90% of the
time on arm64
Changed Bug title to 'ohcount: aborts with segfault or bus error 90%
Package: ohcount
Version: 4.0.0-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-...@lists.debian.org
Dear Maintainer,
ohcount segfaults (and sometimes aborts with a Bus error) on arm64,
almost 90% of the time. I tried this on an up to date arm64 Debian
testing again
Your message dated Wed, 13 Sep 2023 21:44:45 +
with message-id
and subject line Bug#1051752: fixed in uwsgi 2.0.22-2
has caused the Debian Bug report #1051752,
regarding uwsgi: remove uwsgi-plugin-glusterfs on 32 bit architectures
to be marked as done.
This means that you claim that the probl
Your message dated Wed, 13 Sep 2023 21:42:31 +
with message-id
and subject line Bug#1050903: fixed in telegram-desktop 4.9.7+ds-1
has caused the Debian Bug report #1050903,
regarding telegram-desktop: segmentation fault
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 13 Sep 2023 21:35:27 +
with message-id
and subject line Bug#1051828: fixed in pytorch 2.0.1+dfsg-4
has caused the Debian Bug report #1051828,
regarding pytorch: needs-root for autopkgtests?
to be marked as done.
This means that you claim that the problem has been dealt
On 14/08/2023 10.24, attilio giuseppe carolillo wrote:
when do you think 535 drivers will be available in Sid/experimental?
I expect new upstream releases for the 470/525 series end of September
which I'd like to get into the next Debian (old)stable point releases in
October. Thereafter I'll
Source: freeimage
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for freeimage.
CVE-2020-22524[0]:
| Buffer Overflow vulnerability in FreeImage_Load function in
| FreeImage Library 3.19.0(r1828) allows attackers to cuase a deni
Source: kino
Version: 1.3.4+dfsg0-1.1
Severity: serious
Your package came up as a candidate for removal from Debian:
- Dead upstream for a decade
- FTBFS with ffmpeg 5 since 1.5 years (Debian is at ffmpeg 6 by now)
- Depends on various legacy libs (GTK2, Glade)
If you disagree and want to continu
Source: pyside2
Version: 5.15.10-3
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=pyside2&arch=amd64&ver=5.15.10-3%2Bb1&stamp=1694633885&raw=0
Processing commands for cont...@bugs.debian.org:
> tags 1051885 + sid trixie
Bug #1051885 [src:kdevelop] kdevelop: FTBFS with llvm-toolchain-16 as default
Added tag(s) sid and trixie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1051885: https://bugs.debian.org
Source: kdevelop
Version: 4:22.12.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=kdevelop&arch=amd64&ver=4%3A22.12.2-2%2Bb1&stamp=1694630976&raw=0
Ty
Source: qttools-opensource-src
Version: 5.15.10-3
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=qttools-opensource-src&arch=amd64&ver=5.15.10-
Source: postgresql-15
Version: 15.4-2
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=postgresql-15&arch=amd64&ver=15.4-2%2Bb1&stamp=1694632271&
Source: faust
Version: 2.60.3+ds2-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=faust&arch=amd64&ver=2.60.3%2Bds2-1%2Bb1&stamp=1694632020&ra
Processing control commands:
> tag -1 wontfix
Bug #1051849 [dkms] linux-image-6.1.0-12-amd64: Failure to upgrade to
linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64
Added tag(s) wontfix.
> close -1
Bug #1051849 [dkms] linux-image-6.1.0-12-amd64: Failure to upgrade to
linux-image-6.1.0-
Control: tag -1 wontfix
Control: close -1
On Wed, 13 Sep 2023 11:40:28 -0400 Michael Cuffaro
wrote:
CC [M] /var/lib/dkms/rtl88x2bu/5.13.1/build/os_dep/linux/wifi_regd.o
/var/lib/dkms/rtl88x2bu/5.13.1/build/os_dep/linux/wifi_regd.c: In function
‘rtw_regd_init’:
/var/lib/dkms/rtl88x2bu/5.1
Package: libpmix2
Version: 5.0.1-1
Severity: grave
Justification: renders package unusable
Dear maintainer,
Starting with version 5.0.1-1, the libpmix2 package ships a dead symlink
for /usr/lib//libpmix.so.2. For instance:
$ dpkg -c libpmix2_5.0.1-1_amd64.deb | grep libpmix.so
-rw-r--r-- root/r
Processing commands for cont...@bugs.debian.org:
> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'
> tags 1025845 + pending
Bug #1025845 [src:linux] linux: please enable CONFIG_KFENCE
Added tag(s) pending.
> tags 1
Source: gpac
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi
Some of the CVEs in #1033116 seems to not have been addressed (and in
part were addressed in a DSA already). Here a fresh bug for the
remaining ones.
H
Processing commands for cont...@bugs.debian.org:
> tags 1051859 + sid trixie
Bug #1051859 [src:ghdl] ghdl: BD-Uninstallable
Added tag(s) sid and trixie.
> tags 1051860 + sid trixie
Bug #1051860 [src:ccls] ccls: FTBFS with llvm-toolchain-16 das default
Added tag(s) sid and trixie.
> tags 1051863 +
Source: sparse
Version: 0.6.4-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=sparse&arch=amd64&ver=0.6.4-3%2Bb1&stamp=1694628480&raw=0
g++ -L/usr/lib/l
Source: ldc
Version: 1:1.30.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=ldc&arch=amd64&ver=1%3A1.30.0-1%2Bb2&stamp=1694629363&raw=0
[ 14%] Buildin
Source: ccls
Version: 0.20220729-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=ccls&arch=arm64&ver=0.20220729-2%2Bb1&stamp=1694628056&raw=0
/usr/bin/c
Source: ghdl
Version: 2.0.0+dfsg-6.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/package.php?p=ghdl
Dependency installability problem for ghdl on amd64:
ghdl build
Source: clazy
Version: 1.11-4
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=clazy&arch=armhf&ver=1.11-4%2Bb1&stamp=1694627460&raw=0
[ 1%] Bu
Hi,
Thanks Daniel for spotting this, somehow I had missed all notifications
and did not even realise Prometheus was about to be removed from testing :(
I have just ported the patch from Benjamin and after I finish building
the package I will upload it.
On 10/09/2023 06:50, Daniel Swarbrick
Processing control commands:
> reassign -1 dkms
Bug #1051849 [src:linux] linux-image-6.1.0-12-amd64: Failure to upgrade to
linux-image-6.1.0-12-amd64 from linux-image-6.1.0-10-amd64
Bug reassigned from package 'src:linux' to 'dkms'.
No longer marked as found in versions linux/6.1.52-1.
Ignoring r
Control: reassign -1 dkms
Control: tag -1 -ftbfs
On Wednesday, 13 September 2023 17:40:28 CEST Michael Cuffaro wrote:
> Error! Bad return status for module build on kernel: 6.1.0-12-amd64 (x86_64)
> Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more information.
No idea where you got
Your message dated Wed, 13 Sep 2023 16:04:17 +
with message-id
and subject line Bug#1040682: fixed in colord 1.4.6-3
has caused the Debian Bug report #1040682,
regarding FTBFS in colord with meson 1.2.0 rc2
to be marked as done.
This means that you claim that the problem has been dealt with.
Package: pastescript
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
X-Debbugs-Cc: scho...@ubuntu.com
Hi,
In Ubuntu, the attached patch was applied to
Package: src:linux
Version: 6.1.52-1
Severity: grave
Tags: ftbfs
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I ran apt full-upgrade as I usually do
* What exactly d
Control: tag -1 pending
Hello,
Bug #1042342 in yarl 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/packages/yarl/-/commit/56bd15a47b215e9d1d515854e
Processing control commands:
> tag -1 pending
Bug #1042342 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
Ignoring request to alter tags of bug #1042342 to the same tags previously set
--
1042342: https://bugs.debian.or
Control: tags 1042342 + patch
Control: tags 1042342 + pending
Dear maintainer,
I've pushed a commit using a patch cherry-picked from upstream[0] to fix this
issue.
If you don't object, I'll make a team upload of yarl (versioned as 1.8.2-2) with
this fix.
Regards,
[0] https://github.com/aio-li
Processing control commands:
> tags 1042342 + patch
Bug #1042342 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) patch.
> tags 1042342 + pending
Bug #1042342 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuil
Your message dated Wed, 13 Sep 2023 15:04:37 +
with message-id
and subject line Bug#1050942: fixed in blhc 0.13+git20230913.fb2c46d-1
has caused the Debian Bug report #1050942,
regarding FTBFS: Failed 1/1 test programs. 5/246 subtests failed.
to be marked as done.
This means that you claim th
Your message dated Wed, 13 Sep 2023 16:17:40 +0200
with message-id <20230913141740.kjzxnvh2mc7zd...@shell.thinkmo.de>
and subject line Re: Bug#1051847: iproute2 ships configuration files in
/usr/lib violating debian-policy
has caused the Debian Bug report #1051847,
regarding iproute2 ships configu
Processing control commands:
> reopen -1
Bug #1051435 {Done: Timo Röhling }
[src:python-pytest-asyncio] python-pytest-asyncio: failing autopkgtest
'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 reop
Package: iproute2
Version: 6.1.0-3
Severity: serious
Justification: Policy 10.7.2
X-Debbugs-Cc: d...@darkboxed.org
Dear Maintainer,
your iproute2 6.5.0-3 package installs configuration files in
/usr/lib/iproute2. This is a blatant violation of debian-policy
section 10.7.2. "Configuration files /
The following patch should fix the problem.
renzo
diff -Naur grip-4.2.0/debian/control grip-4.2.0.fixed/debian/control
--- grip-4.2.0/debian/control 2016-07-03 23:21:52.0 +0200
+++ grip-4.2.0.fixed/debian/control 2023-09-13 15:20:13.527645376 +0200
@@ -12,6 +12,7 @@
Processing control commands:
> tags -1 + moreinfo
Bug #1051822 [chrony] installed chrony package post-installation script
subprocess returned error exit status 1
Added tag(s) moreinfo.
--
1051822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051822
Debian Bug Tracking System
Contact ow...
Processing control commands:
> tags -1 + moreinfo
Bug #1051822 [chrony] installed chrony package post-installation script
subprocess returned error exit status 1
Ignoring request to alter tags of bug #1051822 to the same tags previously set
--
1051822: https://bugs.debian.org/cgi-bin/bugreport.
Control: tags -1 + moreinfo
Hi Anibal,
Le 2023-09-13 13:52, Anibal Monsalve Salazar a écrit :
> Package: chrony
> Version: 4.2-2
> Severity: critical
>
> # dpkg -i /mnt/apt/archives/chrony_4.4-1_i386.deb
> (Reading database ... 34682 files and directories currently installed.)
> Preparing to unp
Your message dated Wed, 13 Sep 2023 12:04:22 +
with message-id
and subject line Bug#1042181: fixed in trantor 1.5.12+ds-1
has caused the Debian Bug report #1042181,
regarding trantor: FTBFS: MsgBuffer.h:77:5: error: ‘uint8_t’ does not name a
type
to be marked as done.
This means that you cla
Em qua., 13 de set. de 2023 às 03:12, Simon Ruderich
escreveu:
>
> Hi Eriberto,
>
> should be fixed in fb2c46d [2].
>
> Best,
> Simon
>
> [2]:
> https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=fb2c46d23c6052c714729d70d33d54011374689b
Thanks Simon! Have a nice day.
Processing commands for cont...@bugs.debian.org:
> found 1051822 4.4-1
Bug #1051822 [chrony] installed chrony package post-installation script
subprocess returned error exit status 1
Marked as found in versions chrony/4.4-1.
> notfound 1051822 4.2-2
Bug #1051822 [chrony] installed chrony package
Processing control commands:
> severity -1 serious
Bug #1035043 [alex4-data] alex4-data: please request assets be explictly
licensed
Severity set to 'serious' from 'important'
> justification -1 Policy 2.2.1
Unknown command or malformed arguments to command.
--
1035043: https://bugs.debian.org
Your message dated Wed, 13 Sep 2023 09:13:06 +
with message-id
and subject line Bug#1051815: fixed in wasi-libc 0.0~git20230113.4362b18-2
has caused the Debian Bug report #1051815,
regarding Builds invalid wasm32 binaries (1.67->1.68 regression)
to be marked as done.
This means that you claim
Your message dated Wed, 13 Sep 2023 09:12:40 +
with message-id
and subject line Bug#1051815: fixed in rustc 1.69.0+dfsg1-1~exp2
has caused the Debian Bug report #1051815,
regarding Builds invalid wasm32 binaries (1.67->1.68 regression)
to be marked as done.
This means that you claim that the
Your message dated Wed, 13 Sep 2023 09:04:05 +
with message-id
and subject line Bug#1051090: fixed in emacsql 3.1.1+git20230417.6401226+ds-1
has caused the Debian Bug report #1051090,
regarding emacsql: FTBFS: 5 unexpected results
to be marked as done.
This means that you claim that the probl
On Tue, 2023-09-12 at 23:13 +0200, Luca Boccassi wrote:
> On Mon, 11 Sept 2023 at 15:57, Daniel Gröber
> wrote:
> >
> > Hi Luca,
> >
> > On Mon, Sep 11, 2023 at 01:06:06PM +0100, Luca Boccassi wrote:
> > > > I want to question whether removing these conffiles is a good idea at
> > > > all. I'm p
Processing commands for cont...@bugs.debian.org:
> block 1050766 with 1051692
Bug #1050766 [src:classified-ads] classified-ads: FTBFS:
/usr/include/natpmp.h:52:10: fatal error: natpmp_declspec.h: No such file or
directory
1050766 was not blocked by any bugs.
1050766 was not blocking any bugs.
Ad
On Wed, Sep 13, 2023 at 4:04 PM Sebastian Ramacher wrote:
>
> Control: reopen -1
>
> Hi,
>
> the bug was meant to keep the package out of testing as long as it is
> not maintained. Unless you are volunteering to maintain it, this bug is
> not fixed.
>
Yes, it's unfortunately auto-closed by the ch
Processing control commands:
> reopen -1
Bug #1034732 {Done: Shengjing Zhu } [gpac] Keep out of testing
'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 g
Control: reopen -1
Hi,
the bug was meant to keep the package out of testing as long as it is
not maintained. Unless you are volunteering to maintain it, this bug is
not fixed.
Cheers
On 2023-09-13 07:51:07 +, Debian Bug Tracking System wrote:
> Your message dated Wed, 13 Sep 2023 07:49:09 +
Your message dated Wed, 13 Sep 2023 07:49:09 +
with message-id
and subject line Bug#1034732: fixed in gpac 2.2.1+dfsg1-2
has caused the Debian Bug report #1034732,
regarding Keep out of testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated Wed, 13 Sep 2023 07:49:09 +
with message-id
and subject line Bug#1033116: fixed in gpac 2.2.1+dfsg1-2
has caused the Debian Bug report #1033116,
regarding gpac: CVE-2022-3222 CVE-2023-0866 CVE-2022-4202 CVE-2022-43039
CVE-2023-23143 CVE-2023-23144 CVE-2023-23145 CVE-2022-43
Source: pytorch
Version: 2.0.1+dfsg-2
Severity: serious
Hello, I just found this failure on Ubuntu builders.
5393s autopkgtest [13:15:11]: test show_dangling_symlink_if_any: cd
debian/tests ; find /usr -xtype l -print
5393s autopkgtest [13:15:11]: test show_dangling_symlink_if_any:
[--
74 matches
Mail list logo
