On Thu, 2014-01-16 at 10:07 -0700, Michal Jaegermann wrote:
On Wed, Jan 15, 2014 at 10:35:23PM -0800, Adam Williamson wrote:
> On Wed, 2014-01-15 at 23:03 -0700, Michal Jaegermann wrote:
> > On Thu, Jan 16, 2014 at 04:16:43PM +1100, Ankur Sinha wrote:
> > > I know
> > > I can probably fix it removing each package individually etc, but
it'll
> > > take me less time to wipe and reinstall everything.
> >
> > package-cleanup --cleandupes
> >
> > does such removals in one transaction.
>
> I don't want to be too categorical about it, but I deeply distrust that
> option. IIRC, the one time I tried to use it, I found that what it does
> is really *remove* packages,
Well, yes. That why is there. If you want just an information then
Um? I want to remove the duplicate listing from RPM's list of installed
packages, I don't actually want the package 'foo' not to be installed
any more.
> - that is, if you have both 'foo-1.0-1' and
> 'foo-1.0-2' registered as 'installed' and you run
'package-cleanup
> --cleandupes', what seems to happen is you wind up with 'foo-1.0-2'
> registered as 'installed', but *all the files are gone*, or something
> similarly ridiculous. It was badly broken, anyway.
Maybe I was just lucky but most of the time --cleandupes worked for me
just fine. Many years ago I have seen something like you describe for
a few minor packages but that is trivial to fix. I did not run into
something like that ever since.
> I still stick to the old routine for dupe fixing: 'rpm -e --justdb
> --noscripts (older_version)',
This, for a change, leaves you with an asorted leftover files lying
around.
Only if the package's manifest changed between the versions being
upgraded 'from' and 'to' in the update that failed.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net