fish-1.21.12-0.fc5.i386.rpm
  File conflict with: /usr/bin/count
  File conflict with: /usr/share/man/man1/count.1.gz
  => Package conflicts with: html-xml-utils - 3.7-3.fc5.i386

This is unfortunate. The count command in fish uses this very generic names
since it is the recommended way to find out the size of an array:

count $foo

will write the size of the array $foo to the commandline. Because this is one of
the common operations on arrays, it is very often performed in fish
shellscripts, meaning that it would be a big source of bugs, confusion and
backward compatibility woes to try to rename this command on the fish side.

If would be possible to implement count as a shellscript function instead of a
command. I would classify that is a major kludge, but it would certainly be
possible if it is impossible to change this in the html-xml-utils package.

Ping. what do we do with this?
Has there been a change in html-xml-utils or has something changed in fish? Who
can investigate?

Axel, it shouldn't be to tragic to move count to fishcount and check the
occurrences of count in share/*... I had a quick look and I guess it's not too
hard. You can also check if the count problem from html-xml-utils does the same
as your fishcount and if, simply remove it and let fish depend on
%{_bindir}/count - at least in f7 and later.

You'll also need the following exludes in your file-list to not conflict with bash:
%exclude %_mandir/man1/count*
%exclude %_mandir/man1/alias*
%exclude %_mandir/man1/bg*
%exclude %_mandir/man1/bind*
%exclude %_mandir/man1/break*
%exclude %_mandir/man1/builtin
%exclude %_mandir/man1/cd*
%exclude %_mandir/man1/command*
%exclude %_mandir/man1/complete*
%exclude %_mandir/man1/continue*
%exclude %_mandir/man1/dirs*
%exclude %_mandir/man1/eval*
%exclude %_mandir/man1/exec*
%exclude %_mandir/man1/exit*
%exclude %_mandir/man1/fg*
%exclude %_mandir/man1/help*
%exclude %_mandir/man1/jobs*
%exclude %_mandir/man1/popd*
%exclude %_mandir/man1/pushd*
%exclude %_mandir/man1/read*
%exclude %_mandir/man1/return*
%exclude %_mandir/man1/set*
%exclude %_mandir/man1/source*
%exclude %_mandir/man1/trap*
%exclude %_mandir/man1/type*
%exclude %_mandir/man1/ulimit*
%exclude %_mandir/man1/umask*

*** Bug 428349 has been marked as a duplicate of this bug. ***

I don't think anyone would want to access fish specific manpages from outside
fish, so instead of replacing system manpages, they could be placed in a
distinct section, for example '1fish', and fish's man command could be modified
to look there first.

Axel: Does this make sense?

This issue should be fixed in the latest upstream release of fish. Could someone
try building a fish 1.23.0 package and verify that these problems are fixed?

Also, sorry about being so unresponsive on this bug. I actually sent a reply to
this a couple of weeks ago, but it seems to have gotten lost.

If you're happy with rawhide version I can sync it to f8 (and earlier?).

I'm afraid I can't currently test this package as my desktop machine (which was
the one running fedora) died a while ago and I haven't had time to replace it.
But if this package works than I would definitely suggest upgrading the f8 and
f7 package as well, so we can close the conflict bugs as resolved in the current
fedora versions and not just in rawhide.

OK. Pkgs have been built for f8 and f7 as well.

*** Bug 297151 has been marked as a duplicate of this bug. ***

*** Bug 424781 has been marked as a duplicate of this bug. ***