It BuildRequires gcc, which BuildRequires dblatex, which BuildRequires python-which.
I'm rebundling python-which in dblatex, so that should go away.
--
Gwyn Ciesla
she/her/hers
------------------------------------------------
in your fear, seek only peace
in your fear, seek only love
-d. bowie
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, September 10, 2019 8:39 AM, Steven A. Falco <stevenfalco(a)gmail.com>
wrote:
On 9/9/19 6:06 PM, Elliott Sales de Andrade wrote:
> On Mon, 9 Sep 2019 at 18:02, David Sommerseth dazo(a)eurephia.org
wrote:
>
> > On 09/09/2019 23:49, Miro Hrončok wrote:
> >
> > > The following packages are orphaned and will be
retired when they
> > > are orphaned for six weeks, unless someone adopts them. If you know for
sure
> > > that the package should be retired, please do so now with a proper
reason:
> > >
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> >
> > [...snip...]
> >
> > > dsommers: python-which
> >
> > This surprises me quite a lot. I have never been a package
maintainer for
> > this package.
>
> It's not saying you're a package maintainer for this
package. It's
> saying you'll be affected by its orphaning.
> Search for python-which and you'll see it's because python-ethtool
> depends on it, and you maintain that.
I too am apparently affected by python-which. But I'm not sure
how to determine why. I maintain kicad and bvi. Neither directly requires python-which, as
far as I can see:
saf# dnf repoquery --requires kicad | grep python
Last metadata expiration check: 0:00:29 ago on Tue 10 Sep 2019 09:33:45 AM EDT.
libpython3.7m.so.1.0
libpython3.7m.so.1.0()(64bit)
python(abi) = 3.7
python3-wxpython4
saf#
saf# dnf repoquery --requires bvi | grep python
Last metadata expiration check: 0:00:39 ago on Tue 10 Sep 2019 09:33:45 AM EDT.
saf#
How do I determine why I am affected?
Steve (FAS ID stevenfalco)