https://bugzilla.redhat.com/show_bug.cgi?id=1687178
--- Comment #19 from Chris Caron <lead2gold(a)gmail.com> ---
Robert, I stuck with just setting a Provides: entry to the python2-apprise-cli
and python3-apprise-cli because I couldn't think of a clever way to not have a
%package conflict if i renamed both of them to just 'apprise'. You can check it
my workaround here.
SPEC:
https://copr-be.cloud.fedoraproject.org/results/lead2gold/apprise/fedora-...
epel7:
https://koji.fedoraproject.org/koji/taskinfo?taskID=33494613
f29:
https://koji.fedoraproject.org/koji/taskinfo?taskID=33494615
f30:
https://koji.fedoraproject.org/koji/taskinfo?taskID=33494617
f31:
https://koji.fedoraproject.org/koji/taskinfo?taskID=33494619
rawhide:
https://koji.fedoraproject.org/koji/taskinfo?taskID=33494621
COPR:
https://copr.fedorainfracloud.org/coprs/build/868455
You'll be happy to know i built a man page too to start with; I'll probably
need more to explain how configuration files work, but it's a start and also
greatly reduces your rpmlint warnings to just 2 now:
python3-apprise.noarch: W: python-bytecode-without-source
/usr/lib/python3.7/site-packages/apprise/__pycache__/cli.cpython-37.opt-1.pyc
python3-apprise.noarch: W: python-bytecode-without-source
/usr/lib/python3.7/site-packages/apprise/__pycache__/cli.cpython-37.pyc
I'll need to Google these warnings because i don't quite know what it refers to
at this time. The man page (to clear up 2 of the warnings) was added as an
additional Source which has also already been pushed upstream; so it will be
bundled in upcoming releases.
As always, I respect any advice or feedback you have!
Chris
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component