From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30269] New: mock is now part of standard python library
Date: Thu, 23 Mar 2023 21:07:20 +0000 [thread overview]
Message-ID: <bug-30269-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30269
Bug ID: 30269
Summary: mock is now part of standard python library
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
Trying to build fedabipkgdiff on RHEL9.1 fails during configure:
../../libabigail/configure --enable-rpm=yes --enable-ctf --enable-fedabipkgdiff
The problem is that it is looking for the python3-mock module but that doesn't
exist for RHEL9.1 even in EPEL because the package has been deprecated.
$ sudo dnf info python3-mock-4.0.3-5.fc37.noarch
[sudo] password for ben:
Updating Subscription Management repositories.
Last metadata expiration check: 0:18:25 ago on Thu 23 Mar 2023 01:46:50 PM PDT.
Installed Packages
Name : python3-mock
Version : 4.0.3
Release : 5.fc37
Architecture : noarch
Size : 362 k
Source : python-mock-4.0.3-5.fc37.src.rpm
Repository : @System
From repo : fedora
Summary : Deprecated, use unittest.mock from the standard library instead
URL : https://github.com/testing-cabal/mock
License : BSD
Description : This is a deprecated package.
:
: The mock module is now part of the Python standard library,
: available as unittest.mock in Python 3.3 onwards.
:
: https://fedoraproject.org/wiki/Changes/DeprecatePythonMock
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2023-03-23 21:07 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=bug-30269-9487@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).