On Sun, Nov 18, 2007 at 13:31:04 -0500, Jeff Johnson wrote:
> So your expectation is that -e --repackage should also remove
> the package,
Yes.
> I believe (but rpm-4.4.2 was like 3+ years ago) that --repackage takes
> precedence over --erase.
No - every package always is erased when -e --repac
On Nov 18, 2007, at 1:17 PM, Tomasz Pala wrote:
>
>>> # rpm -q --qf "%{name}-%{version}-%{release}.%{arch}\n" libpcap
>>> libpcap-0.9.7-1.athlon
>>> libpcap-0.9.4-1.amd64
>>> # rpm -e libpcap-0.9.7-1.athlon
>>> # rpm -q --qf "%{name}-%{version}-%{release}.%{arch}\n" libpcap
>>> libpcap-0.9.7-1.at
On Sun, Nov 18, 2007 at 12:37:28 -0500, Jeff Johnson wrote:
> You're worried about error msgs like these?
>
> erase unlink of /usr/lib/libsrp.so.0.0.0 failed: No such file or
> directory
No - I've removed these files by hand. I'm worried about not removing
package at all:
> > # rpm -q --qf "%
You're worried about error msgs like these?
erase unlink of /usr/lib/libsrp.so.0.0.0 failed: No such file or
directory
Repackaging is "best effort", its impossible to repackage
content that is not present on the file system. Similarly erasures,
the failure to remove a file that is not present i
# rpm -q --qf "%{name}-%{version}-%{release}.%{arch}\n" libpcap
libpcap-0.9.7-1.athlon
libpcap-0.9.4-1.amd64
# rpm -e libpcap-0.9.7-1.athlon
# rpm -q --qf "%{name}-%{version}-%{release}.%{arch}\n" libpcap
libpcap-0.9.7-1.athlon
libpcap-0.9.4-1.amd64
rpm-4.4.2-46 --rebuilddb and --justdb didn't hel
