f15beta wierdness

[Neal Becker]

mkinitrd --help
Usage:
  pk-command-not-found [OPTION...]

PackageKit Command Not Found

Help Options:
  -h, --help       Show help options

[James Laska]

On Fri, 2011-04-29 at 11:28 -0400, Neal Becker wrote:
> mkinitrd --help
> Usage:
>   pk-command-not-found [OPTION...]
>
> PackageKit Command Not Found
>
> Help Options:
>   -h, --help       Show help options

That is PackageKit implementing the bash command_not_found_handle.  For
details, take a look at ...

# rpm -qf /etc/profile.d/PackageKit.sh 
        PackageKit-command-not-found-0.6.13-1.fc15.x86_64

Using the bash command_not_found_handle, PackageKit attempts to find a
package that provides that missing command.  In your case, PackageKit.sh
is calling ...

/usr/libexec/pk-command-not-found mkinitrd --help

The --help you provided on the initial command-line, is interpreted by
pk-command-not-found ... so you see ...

/usr/libexec/pk-command-not-found --help
        Usage:
          pk-command-not-found [OPTION...]

PackageKit Command Not Found

Help Options:
          -h, --help       Show help options

Unless this is intended, I think it's worth a bug report against
PackageKit-command-not-found so it strips off any options, and only uses
the $1 provided (not the entire arg string $@).

Thanks,
James

[Richard Hughes]

On 29 April 2011 16:47, James Laska  wrote:
> Unless this is intended, I think it's worth a bug report against
> PackageKit-command-not-found so it strips off any options, and only uses
> the $1 provided (not the entire arg string $@).

I thought I fixed this last release -- if not, please file a bug and
I'll sort it out.

Thanks,

Richard.