From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: "J . Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, automated-testing@yoctoproject.org,
Steve Dickson <steved@redhat.com>,
Chuck Lever <chuck.lever@oracle.com>,
libtirpc-devel@lists.sourceforge.net,
Trond Myklebust <trondmy@hammerspace.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 0/3] Remove RPC rup and rusers tests
Date: Thu, 12 May 2022 16:54:18 +0200 [thread overview]
Message-ID: <Yn0fmr2wFUcRdi1h@yuki> (raw)
In-Reply-To: <Yn0d2bVppx36Nwv5@pevik>
Hi!
> > Looks like rstatd wasn't included in distributions to begin with, so
> > there is no point to keep tests for it.
>
> > https://bugs.gentoo.org/show_bug.cgi?id=115806
> > https://access.redhat.com/solutions/34127
> > https://www.ibm.com/support/pages/rstatd-not-installed-or-distributed-suse-linux-enterprise-server-10
>
> Thanks for the links.
> FYI Debian has had it for a long time in rstatd package:
> https://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=contents&keywords=rstatd
> https://packages.debian.org/bullseye/rstatd
> https://tracker.debian.org/pkg/rstatd
>
> but that IMHO no reason to keep these tests.
For debian we have:
https://qa.debian.org/popcon.php?package=rstatd
0.07% of debian installations installed rstatd.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-05-12 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 14:43 [LTP] [RFC PATCH 0/3] Remove RPC rup and rusers tests Petr Vorel
2022-04-28 14:43 ` [LTP] [RFC PATCH 1/3] rpc: Remove rup01.sh test Petr Vorel
2022-04-28 14:43 ` [LTP] [RFC PATCH 2/3] rpc: Remove rusers01.sh test Petr Vorel
2022-04-28 14:43 ` [LTP] [RFC PATCH 3/3] rpc: Move rest of RPC tests to runtest/net.rpc_tests Petr Vorel
2022-04-29 7:48 ` [LTP] [RFC PATCH 0/3] Remove RPC rup and rusers tests Petr Vorel
2022-05-12 14:37 ` Cyril Hrubis
2022-05-12 14:46 ` Petr Vorel
2022-05-12 14:54 ` Cyril Hrubis [this message]
2022-05-12 15:06 ` Petr Vorel
2022-05-31 13:27 ` Cyril Hrubis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yn0fmr2wFUcRdi1h@yuki \
--to=chrubis@suse.cz \
--cc=automated-testing@yoctoproject.org \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=steved@redhat.com \
--cc=trondmy@hammerspace.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox