[SOLVED] HELP-I've broken rpm

[wobo]

Checked, confirmed: problem fixed with new rpmdrake.

For fresh installations of Beta2:
Here the bug still exists. So, best you do an update via urpmi before touching rpmdrake.

[DShelbyD]

I was afraid of that. The problem, I thought, might delay the build of Beta2. When the Beta 2 appeared on schedule, I assumed it was fixed there. IMO, this is not a good sign, not a confidence-builder, especially since it's not mentioned in the release notes. I mean, this update happens before finishing the installation if one chooses to start the connection and apply updates. If that fails, which it will, then one tries immediately after. Again it fails with this weird error. Where is the warning? It's not there.

[wobo]

Now, now!
The solution+update came after ISOs were made. This is a BETA release, not a final. For a final this may well be a release-critical thing causing a delay of the ISOs, but not for a BETA. Was it really so surprising for you that the updated rpmdrake is not in the ISO? You could have known that, just by counting the days.

Anyway BETA releases are for testing and working on them, updating, bug fixing. BETA testers do read the forums or Mailing lists or even Bugzilla. This issue about rpmdrake has been all over the place so I only expect totally new users being surprised, but totally new users do not use BETA releases.

So what is your point?

[DShelbyD]

I'm not interested in an argument. I would have had this fixed prior to a release of Beta2. That's my opinion. It's worth exactly the price charged.

[wobo]

Thx for answering my question about your point.
Our opinions about what a BETA is seem to be very different.

[pmithrandir]

still same issue...

Code: Select all

[root@portablePierre ~]# rm -f /var/lib/rpm/__db*
[root@portablePierre ~]# rpmdb --rebuilddb
[root@portablePierre ~]# urpmi --auto-update
le média « Core Release (distrib1) » est à jour
le média « Core Updates (distrib3) » est à jour
le média « Core Backports (distrib7) » est à jour
le média « Nonfree Release (distrib11) » est à jour
le média « Nonfree Updates (distrib13) » est à jour
le média « Nonfree Backports (distrib17) » est à jour
le média « Tainted Release (distrib21) » est à jour
le média « Tainted Updates (distrib23) » est à jour
le média « Tainted Backports (distrib27) » est à jour
Afin de poursuivre la mise à jour, les paquetages suivants doivent être désinstallés :
meta-task-2-33.mga2.noarch
 (pour installer le paquetage meta-task-2-33.mga2.noarch)
rpm-4.9.1.2-22.mga2.i586
 (pour installer le paquetage rpm-4.9.1.2-22.mga2.i586) (o/N) o
Pour satisfaire les dépendances, les paquetages suivants vont être installés :
   Paquetage                      Version      Révision      Arch   
(média « Core Release (distrib1) »)
  meta-task                      2            33.mga2       noarch 
  rpm                            4.9.1.2      22.mga2       i586   
un espace de 1.6Mo sera libéré.
447Ko de paquets seront récupérés.
Procéder à l'installation des 2 paquetages ? (O/n) o


installation de rpm-4.9.1.2-22.mga2.i586.rpm meta-task-2-33.mga2.noarch.rpm depuis /var/cache/urpmi/rpms
Préparation ...                  #############################################
L'installation a échoué :       paquetage meta-task-1:2-33.mga2.noarch déjà installé
        paquetage rpm-1:4.9.1.2-22.mga2.i586 déjà installé
[root@portablePierre ~]# urpmi --auto --auto-select --replacefiles
Afin de poursuivre la mise à jour, les paquetages suivants doivent être désinstallés :
meta-task-2-33.mga2.noarch
 (pour installer le paquetage meta-task-2-33.mga2.noarch)
rpm-4.9.1.2-22.mga2.i586
 (pour installer le paquetage rpm-4.9.1.2-22.mga2.i586)


installation de rpm-4.9.1.2-22.mga2.i586.rpm meta-task-2-33.mga2.noarch.rpm depuis /var/cache/urpmi/rpms
Préparation ...                  #############################################
L'installation a échoué :       paquetage meta-task-1:2-33.mga2.noarch déjà installé
        paquetage rpm-1:4.9.1.2-22.mga2.i586 déjà installé
[root@portablePierre ~]#


[doktor5000]

This is not the same issue, there's no RPM database error in there.

Also if you post non-english ouput it would certainly be helpful to prefix the command with LC_ALL=C so others can also properly read it without having to use some translation tool.

[jaywalker]

L'installation a échoué :       paquetage meta-task-1:2-33.mga2.noarch déjà installé

Don't worry, that happened to me too. I'd like to say I know a precise cure, but the only way I could get rid of it was by a couple of repeats of "rpmdb --rebuilddb", and perhaps a restart or two of rpmdrake.

If you want me to guess what is happening I would say that the version of the database rpmdrake is looking at doesn't include that "failed" installation. The installation has taken place, so by reuilding the rpm database from installed packages and then re-starting rpmdrake, everything should be correct in the package world. What I mean is, you don't need to install it again, just get it listed in the database.

Richard

[doktor5000]

What I mean is, you don't need to install it again, just get it listed in the database.

That purpose would be fulfilled by rpm's --justdb option, which does just remove or add the DB entries for any given package.
Although you should be knowing what you do if you use something like that.