Re: why does it always break?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Jan 31, 2006, at 6:14 PM, Christian Goetze wrote:

Every time I see a new release of rpm, I get the shivers. Today's breakage:


rpm-4.3.3 ain't exactly a "new release".

rpm -e <list> used to work even if some rpms in the list weren't installed in the first place. As of 4.3.3 (on ia64), attempting to erase a non-installed rpm causes a fatal error. Why? I wanted it gone. If it's already gone, so much for the better. So now I have to first query the list of installed rpms from that list, then erase them (with all sorts of race conditions imaginable between the two operations) - or is there some magic option that I can't find when saying rpm --help that will restore the previous behaviour - or should I use --force?

Hint: If not in bugzilla, then it's not a bug.

But you're forgiven, ia64 ain't exactly pleasant. ;-)

73 de Jeff

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux