Re: xml2rfc rpm
On Mon, 2018-06-04 at 19:55 +0800, Ed Greshko wrote:
On 06/04/18 18:58, Patrick O'Callaghan wrote:
> On Sun, 2018-06-03 at 20:07 -0400, Robert Moskowitz wrote:
> > I see the following rpms in the repo:
> >
> > # grep xml2rfc dnf.lst
> > python2-xml2rfc.noarch 2.5.2-4.fc28 fedora
> > python3-xml2rfc.noarch 2.5.2-4.fc28 fedora
> >
> > yet:
> >
> > # dnf install xml2rfc
> > Last metadata expiration check: 2:22:41 ago on Sun 03 Jun 2018 05:33:23
> > PM EDT.
> > No match for argument: xml2rfc
> > Error: Unable to find a match
>
> Shouldn't that be 'dnf install python3-xml2rfc'?
Yes. But you have to admit that there are inconsistencies in the way things are
done....
[root@f27k ~]# which tracer
/usr/bin/which: no tracer in
(/usr/lib64/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
The available packages are...
python2-dnf-plugin-tracer.noarch 2.0.5-1.fc27 updates
python2-tracer.noarch 0.7.0-1.fc27 updates
python3-dnf-plugin-tracer.noarch 2.0.5-1.fc27 updates
python3-tracer.noarch 0.7.0-1.fc27 updates
tracer-common.noarch
No package named "tracer", yet....
[root@f27k ~]# dnf install tracer
Last metadata expiration check: 0:51:26 ago on Mon 04 Jun 2018 07:03:05 PM CST.
Dependencies resolved.
===================================================================================
Package Arch Version Repository Size
===================================================================================
Installing:
python3-tracer noarch 0.7.0-1.fc27 updates 129 k
[...]
Yes. 'dnf list tracer' and 'dnf info tracer' both show nothing, though
'dnf search tracer' does find it. There appears to be more than one
'name' associated with some packages and how this works is not clearly
documented.
(BTW I don't quite see how 'which' is telling you what packages are
available. Is this some non-default setting? I use 'dnf search' for
that).
poc