Kai Schaetzl wrote on Wed, 26 Mar 2008 12:31:16 +0100:
> I'll dig up all the packages from the yum log and try it.
That still fails for a few packages because of the order I got from the
log. I was able to erase all of them from the rpm db now. But the whole
thing very much looks like a bug, or
Craig White wrote on Tue, 25 Mar 2008 17:26:04 -0700:
> rpm -e --justdb some_package
I had hoped for a solution that "automagically" removes those 50 packages.
Thanks, anyway, I'll dig up all the packages from the yum log and try it.
> rpm --help
It's easy to overlook functionality in that lon
On Wed, 2008-03-26 at 01:09 +0100, Kai Schaetzl wrote:
> I did a "yum groupremove Java" and that failed "somehow". Yum listed all
> group members as "erased", but some rpm packages failed because of missing
> config files or so. As a result none of the 50 packages were removed from
> the rpm da
I did a "yum groupremove Java" and that failed "somehow". Yum listed all
group members as "erased", but some rpm packages failed because of missing
config files or so. As a result none of the 50 packages were removed from
the rpm database, but all of their files seem to have been removed.
How ca
4 matches
Mail list logo