Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: When I am in the directory "~/devel/EPEL Groups" and want to extract buildsys-macros-5-4.el5.noarch.rpm then I get this error: $ rpmdev-extract buildsys-macros-5-4.el5.noarch.rpm error: open of /home/till/devel/EPEL failed: No such file or directory error: open of /home/till/devel/EPEL failed: No such file or directory mkdir: cannot create directory `': No such file or directory Version-Release number of selected component (if applicable): rpmdevtools-5.4-1.fc7 How reproducible: always
Looks like a rpm bug to me: $ mkdir -p "devel/EPEL Groups" $ cd "devel/EPEL Groups" $ wget -q http://buildsys.fedoraproject.org/buildgroups/rhel5/i386/buildsys-macros-5-4.el5.noarch.rpm $ rpm -qp --qf '%{NAME}-%{VERSION}-%{RELEASE}' "$PWD/buildsys-macros-5-4.el5.noarch.rpm" error: open of /home/scop/devel/EPEL failed: No such file or directory error: open of /home/scop/devel/EPEL failed: No such file or directory $ rpm -Uvh "$PWD/buildsys-macros-5-4.el5.noarch.rpm" error: open of /home/scop/devel/EPEL failed: No such file or directory error: open of Groups/buildsys-macros-5-4.el5.noarch.rpm failed: No such file or directory $ rpm -q rpm rpm-4.4.2-46.fc7.x86_64 Also, the exit status of the failing "rpm -qp ..." command above is 0, so I can't use that do detect failures in rpmdev-extract. I think it should be changed to indicate failure if there is one.
Mostly a dupe of bug #217258 but the incorrect exit status not mentioned there...
rpmdevtools workarounds: * rpmdev-extract: http://cvs.fedora.redhat.com/viewcvs/fedora-rpmdevtools/rpmdev-extract?root=fedora&r1=1.1&r2=1.2 * rpmls: http://cvs.fedora.redhat.com/viewcvs/fedora-rpmdevtools/rpmls?root=fedora&r1=1.1&r2=1.2
User pnasrat's account has been closed
*** Bug 217258 has been marked as a duplicate of this bug. ***
I was about to enter a new bug until I found this one. I've just installed FC8 in a VMware instance to try it out. Description of problem: If I hand rpm a path to a package that has a space in the name, rpm treats it as two arguments separated by the space instead of one, even though the space is either escaped or quoted. This was spotted on a VMware installation where the VMware Tools are mounted on "/media/VMware Tools" by default. Version-Release number of selected component (if applicable): 4.4.2.2-3.fc8, 4.4.2.2-7.fc8, 4.4.2-32 (fc6), and 4.4.2-37.el5 How reproducible: Every time Steps to Reproduce: 1. # touch '/tmp/test rpm-1.0-1.noarch.rpm' 2a. # rpm -ivh '/tmp/test rpm-1.0-1.noarch.rpm' 2b. # rpm -ivh /tmp/test\ rpm-1.0-1.noarch.rpm Actual results: error: open of /tmp/test failed: No such file or directory error: open of rpm-1.0-1.noarch.rpm failed: No such file or directory Expected results: /tmp/test rpm-1.0-1.noarch.rpm: not an rpm package (or package manifest): Additional info: I can confirm that this bug also exists on Fedora Core 6 and Red Hat Enterprise Linux 5 (at work).
This is a very old bug -- I can also confirm that it existed on RHEL 3 (rpm-4.2.3-30_nonptl).
Fixed in 4.4.2.3-0.1.rc1: [pmatilai@localhost ~]$ rpm -qp --qf "%{name} %{version}\n" ~/"dir with spaces"/SRPMS/* file 4.21 popt 1.12