On Mon, Nov 09, 2020 at 12:09:00PM +0100, Miro Hrončok wrote:
> rjones: xinetd, numad
Your "packager dashboard"[1] which I found for the first time today is
very useful!
Turns out the problem for my package is this weird ol' dependency chain:
coccinelle -> git -> cvs -> xinetd
Well the first part of that is understandable, because Cocci uses git
to apply patches (ie. autosetup -S git).
cvs -> xinetd is sort of understandable too.
git -> cvs however(!) It turns out that git has a cvs import
subpackage. But I wonder if git actually needs cvs around at build
time to create this? I commented out the BR: cvs, cvsps lines in the
spec file and it built a cvs import subpackage just fine for me.
----------------------------------------------------------------------
diff --git a/git.spec b/git.spec
index 6081678..f3294b6 100644
--- a/git.spec
+++ b/git.spec
@@ -199,8 +199,8 @@ BuildRequires: apr-util-bdb
# endif fedora >= 27
BuildRequires: bash
%if %{with cvs}
-BuildRequires: cvs
-BuildRequires: cvsps
+#BuildRequires: cvs
+#BuildRequires: cvsps
%endif
# endif with cvs
%if %{use_glibc_langpacks}
----------------------------------------------------------------------
Rich.
[1] https://packager.fedorainfracloud.org/
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
