public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Adam Williamson <awilliam@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/openqa] f44: Fix a couple of incorrect -devel package deps
Date: Thu, 18 Jun 2026 06:01:23 GMT [thread overview]
Message-ID: <178176248398.1.1683538891865725923.rpms-openqa-90ac778e7ea5@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/openqa
Branch : f44
Commit : 90ac778e7ea58b5dc5d41f60e8b79c76ea4c71a6
Author : Adam Williamson <awilliam@redhat.com>
Date : 2026-06-18T08:00:01+02:00
Stats : +3/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/openqa/c/90ac778e7ea58b5dc5d41f60e8b79c76ea4c71a6?branch=f44
Log:
Fix a couple of incorrect -devel package deps
I inadvertently readded xorg-x11-fonts, and our Perl::Critic
is versioned a bit differently (no .0).
---
diff --git a/openqa.spec b/openqa.spec
index c44267e..6b42788 100644
--- a/openqa.spec
+++ b/openqa.spec
@@ -91,8 +91,9 @@
# SUSE has python3-yamllint but we just have yamllint,
# SUSE has python3-gitlint and python3-ruff but we just have gitlint and ruff
# shfmt is omitted as our package for it was orphaned and retired
+# Perl::Critic doesn't have a third version component on Fedora
# The following line is generated from dependencies.yaml (upstream)
-%define style_check_requires ShellCheck perl(Code::TidyAll) perl(Perl::Critic) >= 1.156.0 perl(Pod::Markdown) perl(Test::Perl::Critic) gitlint ruff yamllint
+%define style_check_requires ShellCheck perl(Code::TidyAll) perl(Perl::Critic) >= 1.156 perl(Pod::Markdown) perl(Test::Perl::Critic) gitlint ruff yamllint
# diff from SUSE: perl(Devel::Cover::Report::Codecovbash) dropped because
# it's not in Fedora (this means you can't run 'make coverage-codecov')
# The following line is generated from dependencies.yaml (upstream)
@@ -102,7 +103,7 @@
# multiple binary packages) and I can't find any reason for it
# diff from SUSE 2: we don't have perl(Test::CheckGitStatus) packaged
# The following line is generated from dependencies.yaml (upstream)
-%define devel_no_selenium_requires %build_requires %cover_requires %qemu %style_check_requires %test_requires curl make pandoc perl(Perl::Tidy) perl(TAP::Harness::JUnit) postgresql-devel python3-weasyprint rsync sudo tar xorg-x11-fonts
+%define devel_no_selenium_requires %build_requires %cover_requires %qemu %style_check_requires %test_requires curl make pandoc perl(Perl::Tidy) perl(TAP::Harness::JUnit) postgresql-devel python3-weasyprint rsync sudo tar
# diff from SUSE: chromedriver dropped as we don't package it
# that makes this look fairly silly, but we want to follow the SUSE
# spec as close as we can
reply other threads:[~2026-06-18 6:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178176248398.1.1683538891865725923.rpms-openqa-90ac778e7ea5@fedoraproject.org \
--to=awilliam@redhat.com \
--cc=git-commits@fedoraproject.org \
/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