-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 18 Feb 2003 13:34:48 +0100, Ronald Hermans wrote:
> Downloaded the package again and renamed it to kernel-2.4.18-24.8.0.i686.rpm
> (removing the [1] that was in the name.
Ah! Great info. That explains the thing. I did not assume the actual
file contained "[1]", and even if it did, that it would create
problems.
> kernel-2[1].4.18-24.8.0.i686.rpm
It seems, internally RPM applies pattern matching, when it sees
the square brackets, and hence expects file
kernel-21.4.18-24.8.0.i686.rpm
^
to be present. However, when the pattern expands to something not
found on disk, shouldn't it print an error rather than just
D: found 0 source and 0 binary packages
in ultra-verbose mode?
$ ls bash-2[1].05b-20.i386.rpm
bash-2[1].05b-20.i386.rpm
$ ls bash-2\[1\].05b-20.i386.rpm
bash-2[1].05b-20.i386.rpm
$ rpm -ivvh bash-2[1].05b-20.i386.rpm
D: found 0 source and 0 binary packages
$ rpm -ivvh bash-2\[1\].05b-20.i386.rpm
D: found 0 source and 0 binary packages
Upon verifying, it does not have any problems like that:
$ rpm -K bash-2[1].05b-20.i386.rpm
bash-2[1].05b-20.i386.rpm: md5 gpg OK
$ rpm -K bash-2\[1\].05b-20.i386.rpm
bash-2[1].05b-20.i386.rpm: md5 gpg OK
With just one opening bracket, it does accept the file, too:
$ cp bash*.rpm a\[
$ rpm -i --test a\[
error: failed dependencies:
-snip-
With a closing bracket added, it fails again:
$ cp bash*.rpm a\[\]
$ rpm -ivv --test a\[\]
D: found 0 source and 0 binary packages
Any RPM wizard reading this? ;-)
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+Ukdp0iMVcrivHFQRAufVAJ97WW5mp83BfDhLZmhBwCnl7dM29ACeK6/N
P1Y0+jMbtGx+WSL1mnP5FBQ=
=l/q1
-----END PGP SIGNATURE-----
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
