Processing commands for cont...@bugs.debian.org:
> reassign 1011044 src:tiledb 2.8.3-2
Bug #1011044 {Done: Dirk Eddelbuettel } [libtiledb2.8]
libtiledb2.8 needs Breaks+Replaces: libtiledb2.7
Warning: Unknown package 'libtiledb2.8'
Bug reassigned from package 'libtiledb2.8' to 'src:tiledb'.
No lon
Processing control commands:
> tags 943303 + patch
Bug #943303 [src:yasm] yasm: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #943303 to the same tags previously set
> tags 943303 + pending
Bug #943303 [src:yasm] yasm: Python2 removal in sid/bullseye
Ignoring request to alt
Control: tags 943303 + patch
Control: tags 943303 + pending
Control: tags 997338 + patch
Control: tags 997338 + pending
Dear maintainer,
I've prepared an NMU for yasm (versioned as 1.3.0-2.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebast
Processing control commands:
> tags 943303 + patch
Bug #943303 [src:yasm] yasm: Python2 removal in sid/bullseye
Added tag(s) patch.
> tags 943303 + pending
Bug #943303 [src:yasm] yasm: Python2 removal in sid/bullseye
Added tag(s) pending.
> tags 997338 + patch
Bug #997338 [src:yasm] yasm: FTBFS: c
Hi,
On Tue, May 17, 2022 at 09:36:11PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:gitit package:
>
> #992297: gitit: CVE-2021-38711
>
> It has been closed by Debian FTP Masters
> (reply to Scott Talbe
On 2022-05-17 16:57:55 +0200, Axel Beckert wrote:
> > Concerning this bug, it was reported upstream 3 months ago, and
> > there is still no reaction there.
>
> You are aware, that at least for mosh the Debian package maintainer
> and main upstream developer of Mosh is the same person? So actually
Source: redis
Version: 5:6.0.16-2
Severity: serious
Tags: ftbfs sid bookworm
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=redis&arch=amd64&ver=5%3A6.0.16-2%2Bb1&stamp=1652566704&raw=
Source: ovn
Version: 21.06.0+ds1-5
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=ovn&arch=armhf&ver=21.06.0%2Bds1-5&stamp=1652705748&raw=0
/usr/bin/make
Processing control commands:
> tags 994672 + patch
Bug #994672 [src:open-isns] open-isns FTBFS: error: ‘sigrelse’ is deprecated
Added tag(s) patch.
> tags 994672 + pending
Bug #994672 [src:open-isns] open-isns FTBFS: error: ‘sigrelse’ is deprecated
Added tag(s) pending.
--
994672: https://bugs.d
Control: tags 994672 + patch
Control: tags 994672 + pending
Dear maintainer,
I've prepared an NMU for open-isns (versioned as 0.101-0.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru open-isns-0.100/ChangeLog open-i
Package: xygrib
Version: 1.2.6.1-1
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
Tags: patch
xygrib build-depends on libgrib2c-dev which is no longer built by the g2clib
source package. It is still present in unstable as a cruft package, but is
Hi,
17/05/2022 19:02, John Paul Adrian Glaubitz :
Hello Agathe!
On 5/17/22 18:48, Agathe Porte wrote:
I do not know when that was done, but the two latest Fedora releases have been
using >=35
versions which properly support OpenSSL 3.0 [1]. I have opened #1011155 in
order to discuss
why we c
Your message dated Tue, 17 May 2022 21:33:46 +
with message-id
and subject line Bug#992297: fixed in gitit 0.15.1.0+dfsg-1
has caused the Debian Bug report #992297,
regarding gitit: CVE-2021-38711
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
close 1008379 1.5.1-1
thanks
Tested the build of the new package release in sbuild
sid chroot and did not see any problems.
--
Valentin
Version 3.0.7 seems to be be passing most of the time on armhf, though there
were
a few failures duing attempts to migrate gcc-12. The failures appear to be
timeouts.
Unfortunately 3.0.7 seems to be pretty consistently failing on s390x :(
Processing commands for cont...@bugs.debian.org:
> close 1008379 1.5.1-1
Bug #1008379 [src:synfigstudio] synfigstudio: FTBFS: _clock_system.h:34:27:
error: using-declaration for non-member at class scope
Marked as fixed in versions synfigstudio/1.5.1-1.
Bug #1008379 [src:synfigstudio] synfigstudi
Source: opennds
Version: 9.7.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=opennds&ver=9.7.0-1
...
dh_fixperms
chmod a-x debian/opennds/etc/opennds/fas-hid.php
chmod: cannot access 'debian/opennds/etc/opennds/fas-hid.php': No such file or
directory
make[1]: ***
Hi,
with this MR applied, it does not crash at least.
https://salsa.debian.org/georgesk/cwiid/-/merge_requests/1
Not tested yet.
Bernd
--
Bernd ZeimetzDebian GNU/Linux Developer
http://bzed.dehttp://www.debian.org
GPG Fingerprin
Package: apertium-recursive
Version: 1.1.0-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Dear maintainers,
The new version of apertium-recursive FTBFS in Ubuntu on most archs because
of incorrect handling of EOF condition from fge
Processing control commands:
> found -1 pidgin/2.14.9-2
Bug #1011166 [src:pidgin, src:chatty] pidgin breaks chatty autopkgtest: error
while loading shared libraries: libjabber.so.0
Marked as found in versions pidgin/2.14.9-2.
> found -1 chatty/0.6.3-1
Bug #1011166 [src:pidgin, src:chatty] pidgin
Source: pidgin, chatty
Control: found -1 pidgin/2.14.9-2
Control: found -1 chatty/0.6.3-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of pidgin the autopkgtest of chatty fails in
testing when that a
Your message dated Tue, 17 May 2022 22:37:59 +0200
with message-id
and subject line Re: pidgin: ftbfs with autoconf 2.70
has caused the Debian Bug report #978881,
regarding pidgin: ftbfs with autoconf 2.70
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Processing commands for cont...@bugs.debian.org:
> severity 976439 grave
Bug #976439 [wminput] wminput: Aborts with "undefined symbol:
PyVarObject_CallFunction"
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976439: https
Processing commands for cont...@bugs.debian.org:
> forwarded 1011127 https://github.com/openssl/openssl/issues/18334
Bug #1011127 [libssl3] libssl3 breaks systems vith VIA Nehemiah cpu
Set Bug forwarded-to-address to
'https://github.com/openssl/openssl/issues/18334'.
>
End of message, stopping pr
Processing control commands:
> severity -1 serious
Bug #1011165 [mediathekview] org.h2.jdbc.JdbcSQLSyntaxErrorException: schema
"MEDIATHEKVIEW" not found
Severity set to 'serious' from 'important'
--
1011165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011165
Debian Bug Tracking System
C
It's a pleasure!
We cannot write instructions to cover every eventually; that is
effectively impossible. But it seems like you did the right thing to
sort out your problem, which I am pleased to hear.
Best wishes,
Julian
On Tue, May 17, 2022 at 07:42:37PM +0200, epsommum...@virgilio.it wrot
Processing commands for cont...@bugs.debian.org:
> tag 1006393 patch
Bug #1006393 [src:libewf] libewf: FTBFS with OpenSSL 3.0
Added tag(s) patch.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1006393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10
control: forward -1 https://github.com/openssl/openssl/issues/18334
On 2022-05-17 16:01:35 [+0200], Wolfgang Walter wrote:
>
> Yes, with libssl3_3.0.3-4.noendbr_i386.deb this is fixed.
perfect, thank you for the confirmation.
I forwarded it upstream and I hope to have something for the next
uplo
Processing commands for cont...@bugs.debian.org:
> severity 1009282 normal
Bug #1009282 [src:live-wrapper] Should live-wrapper be removed?
Severity set to 'normal' from 'serious'
> reassign 1009282 ftp.debian.org
Bug #1009282 [src:live-wrapper] Should live-wrapper be removed?
Bug reassigned from p
severity 1009282 normal
reassign 1009282 ftp.debian.org
retitle 1009282 RM: live-wrapper -- RoQA; Depends on Python 2, depends on
removed package
thanks
Reassigning for removal.
Cheers,
Moritz
Processing commands for cont...@bugs.debian.org:
> severity 1009280 normal
Bug #1009280 [src:python-passfd] Should python-passfd be removed?
Severity set to 'normal' from 'serious'
> reassign 1009280 ftp.debian.org
Bug #1009280 [src:python-passfd] Should python-passfd be removed?
Bug reassigned fr
severity 1009280 normal
reassign 1009280 ftp.debian.org
retitle 1009280 RM: python-passfd -- RoQA; Depends on Python 2, no reverse deps
thanks
Reassigning for removal.
Cheers,
Moritz
Processing commands for cont...@bugs.debian.org:
> severity 1009276 normal
Bug #1009276 [src:fsl] Should fsl be removed?
Severity set to 'normal' from 'serious'
> reassign 1009276 ftp.debian.org
Bug #1009276 [src:fsl] Should fsl be removed?
Bug reassigned from package 'src:fsl' to 'ftp.debian.org'
severity 1009276 normal
reassign 1009276 ftp.debian.org
retitle 1009276 RM: fsl -- RoM; Depends on Python 2, FTBFS, unmaintained
thanks
Reassigning for removal.
Thank you very much !
Your command did not work in Spyder's console on the desktop, first because of
the 3 at the end of pip, then because pressing the Y key at the prompt did not
do anything. After googling how to force uninstall I found the command that
worked for the desktop :
pip uninstall
Hello Agathe!
On 5/17/22 18:48, Agathe Porte wrote:
> I do not know when that was done, but the two latest Fedora releases have
> been using >=35
> versions which properly support OpenSSL 3.0 [1]. I have opened #1011155 in
> order to discuss
> why we cannot just update to latest upstream version
Processing commands for cont...@bugs.debian.org:
> tags 1010377 + pending
Bug #1010377 [v2ray] V2Ray CVE-2021-4070 DoS by Authenticated VMess Server
patch not applied
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1010377: https://bugs.debi
Processing commands for cont...@bugs.debian.org:
> tags 1009818 + pending
Bug #1009818 [v2ray] V2Ray 4.34.0-5 (Debian Unstable ver.) Crashes when VMess
Protocol is Used because an unsynchronized update of Golang and V2Ray - HMAC
constructor fix not applied on Debian
Added tag(s) pending.
> thank
Package: golang-gopkg-libgit2-git2go.v31
Followup-For: Bug #1010505
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Control: tags -1 patch
This package builds (and tests) fine, except for this strict version check
in the test.
Testing for versions instead of featu
Processing control commands:
> tags -1 patch
Bug #1010505 [golang-gopkg-libgit2-git2go.v31] golang-gopkg-libgit2-git2go.v31
autopkgtest failure with libgit2 1.3
Added tag(s) patch.
--
1010505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010505
Debian Bug Tracking System
Contact ow...@bug
Hi,
17/05/2022 08:43, John Paul Adrian Glaubitz :
Hi!
Looks like an upgrade to at least v35.0.0 is needed to fix this issue:
https://github.com/pyca/cryptography/issues/7039#issuecomment-1088566628=
Not necessarily. One of the Python core developers, Christian Heimes, actually
backported fixe
Dear RB68,
On Tue, May 17, 2022 at 04:54:19PM +0200, RB68 wrote:
> Package: spyder
> Version: 5.3.0+dfsg1-7
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: epsommum...@virgilio.it
>
> Dear Maintainer,
>
> I upgraded Spyder 4.2.1 to 5.3 both on my main desktop PC and i
Your message dated Tue, 17 May 2022 17:13:21 +0100
with message-id
and subject line Re: Bug#1011152: spyder: Console not starting. Spyder alerts :
iPython 7.31.1 & qtconsole 5.3.0 not installed. But they are !
has caused the Debian Bug report #1011152,
regarding spyder: Console not starting. Spyd
In the upstream issue it's noted that javacc 6.1.3 was never released:
"
This tagged release may or may not be released, but is tagged here so
that we maintain a history prior to merging in Francis' substantial
changes.
"
https://github.com/javacc/javacc/releases/tag/release_6_1_3
6.1.2 is t
Hi Vincent,
Vincent Lefevre wrote:
> > > Shouldn't Debian use -Wno-error=deprecated-declarations to ignore
> > > the use of deprecated functions?
> >
> > No, in contrary. These kind of problems only appear in Debian Unstable
> > which is our development branch. And there we should see such issues
On 12/05/2022 14.21, Andreas Beckmann wrote:
That dependency problem should resolve automatically once src:linux gets
decrufted.
But we should probably have a better way to enumerate "all
linux-header-* packages" in dkms-autopkgtest ... and skip cruft ...
Nope, that is a problem in src:linux-s
Hi Axel,
On 2022-05-17 14:26:51 +0200, Axel Beckert wrote:
> Vincent Lefevre wrote:
> > Shouldn't Debian use -Wno-error=deprecated-declarations to ignore
> > the use of deprecated functions?
>
> No, in contrary. These kind of problems only appear in Debian Unstable
> which is our development bran
Am 2022-05-17 15:34, schrieb Sebastian Andrzej Siewior:
On 2022-05-17 12:53:07 [+0200], Wolfgang Walter wrote:
Systems with VIA Nehemiah cpu break after upgrading unstable. All
commands
using libssl3 fail with
…
lscpu shows:
Architecture:i686
CPU op-mode(s):
Your message dated Tue, 17 May 2022 13:33:41 +
with message-id
and subject line Bug#999716: fixed in ruby-omniauth-google-oauth2 1.0.1-1
has caused the Debian Bug report #999716,
regarding ruby-omniauth-google-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR:
Test "ruby2.7" failed: NoMethod
Your message dated Tue, 17 May 2022 13:33:48 +
with message-id
and subject line Bug#999722: fixed in ruby-omniauth-openid 2.0.1-1
has caused the Debian Bug report #999722,
regarding ruby-omniauth-openid: FTBFS with ruby-omniauth 2.0.x: ERROR: Test
"ruby2.7" failed: /usr/lib/ruby/vendor_ruby/r
On 2022-05-17 12:53:07 [+0200], Wolfgang Walter wrote:
> Systems with VIA Nehemiah cpu break after upgrading unstable. All commands
> using libssl3 fail with
…
> lscpu shows:
>
> Architecture:i686
> CPU op-mode(s): 32-bit
…
> Flags: fp
Processing control commands:
> clone -1 -2 -3 -4 -5 -6 -7 -8
Bug #1011140 [src:nvidia-graphics-drivers] nvidia-graphics-drivers:
CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191,
CVE-2022-28192
Bug 1011140 cloned as bugs 1011141-1011147
> reassign -2 src:nvidia-grap
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-28181,
CVE-2022-28185
Control: tag -2 + wontfix
Package: python-omegaconf
Version: 2.1.0~rc1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sl...@ubuntu.com
Dear Maintainer,
The python-omegaconf package fails to build from source, whenever the host
is not connected t
Your message dated Tue, 17 May 2022 12:33:55 +
with message-id
and subject line Bug#1011131: fixed in josm 0.0.svn18427+dfsg-2
has caused the Debian Bug report #1011131,
regarding josm: FTBFS with JavaCC 6
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Hi Vincent,
Vincent Lefevre wrote:
> Shouldn't Debian use -Wno-error=deprecated-declarations to ignore
> the use of deprecated functions?
No, in contrary. These kind of problems only appear in Debian Unstable
which is our development branch. And there we should see such issues
rather early than l
Processing control commands:
> tags -1 pending
Bug #1011131 [src:josm] josm: FTBFS with JavaCC 6
Added tag(s) pending.
--
1011131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 pending
On 5/17/22 13:27, Emmanuel Bourg wrote:
This can be fixed by building with the javacc5 package instead of javacc
Thanks for this workaround, I'll use that for the time being.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6
Processing commands for cont...@bugs.debian.org:
> close 1011025 0.11.4-2
Bug #1011025 [src:golang-github-containerd-stargz-snapshotter]
golang-github-containerd-stargz-snapshotter FTBFS: cannot find package
"github.com/ipfs/go-cid"
Marked as fixed in versions
golang-github-containerd-stargz-sn
Processing commands for cont...@bugs.debian.org:
> tags 1011131 + upstream
Bug #1011131 [src:josm] josm: FTBFS with JavaCC 6
Added tag(s) upstream.
> forwarded 1011131 https://github.com/simonpoole/OpeningHoursParser/issues/72
Bug #1011131 [src:josm] josm: FTBFS with JavaCC 6
Set Bug forwarded-to-
Processing control commands:
> severity -1 normal
Bug #1011130 [libpipewire-0.3-0] libpipewire-0.3-0: should not recommend
pipewire
Severity set to 'normal' from 'critical'
--
1011130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011130
Debian Bug Tracking System
Contact ow...@bugs.debian
Control: severity -1 normal
On 2022-05-17 13:20:30, Vincent Lefevre wrote:
> Package: libpipewire-0.3-0
> Version: 0.3.51-1
> Severity: critical
> Justification: breaks unrelated software
>
> Several packages depend on libpipewire-0.3-0 in order to have
> pipewire *support* (but they don't need p
Source: josm
Version: 0.0.svn18427+dfsg-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
josm fails to build with JavaCC 6:
[javac]
/<>/src/ch/poole/openinghoursparser/OpeningHoursParserTokenManager.java:1182:
error: incompatible types: possible lossy conversion from int to char
[ja
Package: libpipewire-0.3-0
Version: 0.3.51-1
Severity: critical
Justification: breaks unrelated software
Several packages depend on libpipewire-0.3-0 in order to have
pipewire *support* (but they don't need pipewire: the user may
want to use pulseaudio). However, libpipewire-0.3-0 currently
has "R
Processing commands for cont...@bugs.debian.org:
> found 937234 1.0.9-2
Bug #937234 [src:pam-python] pam-python: Python2 removal in sid/bullseye
Marked as found in versions pam-python/1.0.9-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937234: https://bugs.de
Your message dated Tue, 17 May 2022 07:01:28 -0400
with message-id
and subject line Re: mutter: Let gtk4 4.6.3+ds1-2 migrate to testing first
has caused the Debian Bug report #1010813,
regarding mutter: Let gtk4 4.6.3+ds1-2 migrate to testing first
to be marked as done.
This means that you claim
Package: libssl3
Version: 3.0.3-4
Severity: grave
Systems with VIA Nehemiah cpu break after upgrading unstable. All
commands using libssl3 fail with
traps: modprobe[2002] trap invalid opcode ip:b7c14700 sp:bfed3238
error:0 in libcrypto.so.3[b7ac+24f000]
traps: sshd[1969] trap invalid opco
Le mar. 17 mai 2022 à 12:00, Adam Borowski a écrit :
> Source: iotjs
> Version: 1.0+715-1
> Severity: serious
> Justification: In the opinion of a QA person the package is unsuitable for
> release.
>
> Hi!
> This package appears to be unmaintained, and:
> * has a large set of CVEs reported. They
On 2022-02-13 21:58:36 +0100, Sebastian Andrzej Siewior wrote:
> Your package is failing to build using OpenSSL 3.0 with the
> following error:
>
> | c++ -DHAVE_CONFIG_H -I. -I../.. -I./../util -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -pedantic -Wno-long-long -Weffc++
> -Wmissin
Source: iotjs
Version: 1.0+715-1
Severity: serious
Justification: In the opinion of a QA person the package is unsuitable for
release.
Hi!
This package appears to be unmaintained, and:
* has a large set of CVEs reported. They are also untriaged and have seen
no maintainer response.
* blocks Py
Your message dated Tue, 17 May 2022 09:33:53 +
with message-id
and subject line Bug#1006513: fixed in openpace
1.1.2+ds+git20220117+453c3d6b03a0-1
has caused the Debian Bug report #1006513,
regarding openpace: FTBFS with OpenSSL 3.0
to be marked as done.
This means that you claim that the pr
Your message dated Tue, 17 May 2022 08:40:43 +
with message-id
and subject line Bug#1011107: fixed in waylandpp 1.0.0-3
has caused the Debian Bug report #1011107,
regarding binary packages should conflict/replace older ones
to be marked as done.
This means that you claim that the problem has
Package: libpython2.7-stdlib
Version: 2.7.18-13.1
Severity: serious
libssl1.1 is no longer being built by src:openssl.
Processing commands for cont...@bugs.debian.org:
> tags 999725 + experimental
Bug #999725 {Done: Mohammed Bilal }
[src:ruby-omniauth-saml] ruby-omniauth-saml: FTBFS with ruby-omniauth 2.0.x:
ERROR: Test "ruby2.7" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in blo
Processing commands for cont...@bugs.debian.org:
> tags 104 + sid bookworm
Bug #104 [src:nvidia-cuda-toolkit] nivdia-cuda-toolkit: hardcodes
dependencies on libssl1.1
Added tag(s) sid and bookworm.
> severity 104 serious
Bug #104 [src:nvidia-cuda-toolkit] nivdia-cuda-toolkit: hard
Processing control commands:
> reopen -1
Bug #1006008 {Done: John Paul Adrian Glaubitz }
[src:python-cryptography] python-cryptography: FTBFS with OpenSSL 3.0
Bug reopened
Ignoring request to alter fixed versions of bug #1006008 to the same values
previously set
--
1006008: https://bugs.debian
Control: reopen -1
On 5/17/22 08:50, John Paul Adrian Glaubitz wrote:
> I just noticed the patches for OpenSSL 3.0 support have already been added to
> the
> Debian package [1]. I also verified that the package builds fine in unstable
> with OpenSSL 3.0.
>
> Therefore closing this bug report.
H
77 matches
Mail list logo
