public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Maxwell G <maxwell@gtmx.me>
To: git-commits@fedoraproject.org
Subject: [rpms/scancode-toolkit] rawhide: Update test ignores and fix FTBFS (rhbz#2466652)
Date: Sat, 30 May 2026 17:44:41 GMT [thread overview]
Message-ID: <178016308161.1.4126904327696941560.rpms-scancode-toolkit-fa8de0937812@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/scancode-toolkit
Branch : rawhide
Commit : fa8de093781242565f22eae033b49a55a93c8381
Author : Maxwell G <maxwell@gtmx.me>
Date : 2026-05-30T01:09:57-05:00
Stats : +4/-4 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/scancode-toolkit/c/fa8de093781242565f22eae033b49a55a93c8381?branch=rawhide
Log:
Update test ignores and fix FTBFS (rhbz#2466652)
Re-enable a set of tests that were fixed upstream and disable another test that
were likely broken by improperly tested Python lib dependency updates :(.
---
diff --git a/scancode-toolkit.spec b/scancode-toolkit.spec
index 9a1be7d..156f393 100644
--- a/scancode-toolkit.spec
+++ b/scancode-toolkit.spec
@@ -155,12 +155,12 @@ export PYTHONPATH="$(pwd)/src"
test_package_list_command and not
test_get_file_info_include_size and not
test_scan_cli_help and not
- %dnl These test failures have to do with the handling of tempfiles in the CLI
- %dnl and don't seem particularly important. Disable them for now
- test_scan_keep_temp_files_is_false_by_default and not
- test_scan_keep_temp_files_keeps_files and not
%dnl https://github.com/aboutcode-org/scancode-toolkit/issues/4540
test_license_reference_to_file_beside_package_manifest and not
+ %dnl https://bugzilla.redhat.com/show_bug.cgi?id=2466652
+ %dnl This failure only impacts scanning of Windows PE executables,
+ %dnl which we do not particularly care about.
+ test_win_pe_tre4_dll and not
%dnl Add new entries above this line.
placeholder}'
%endif
reply other threads:[~2026-05-30 17:44 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=178016308161.1.4126904327696941560.rpms-scancode-toolkit-fa8de0937812@fedoraproject.org \
--to=maxwell@gtmx.me \
--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