Skip to main content

Mandriva urpmi

Mageia linuxpackage management has added some enhancements to their urpmi tool. One of the newest is the ability to remove 'orphaned' packages from the system. Orphans are rpm packages that were installed as a dependency for some other package and said other package has been removed, but the orphan remains.

The canonical source of information about urpmi can be found at the Mageia Wiki.

The file /var/lib/rpm/installed-through-deps.list contains a list of packages installed indirectly and the package manager uses this list to determine 'orphans' when the follow command is run to remove orphans:

# urpme --auto-orphans

If you run that command and the list of orphans is incorrect (it wants to remove packages that you know should not be uninstalled), the fix is simple. Just edit the file /var/lib/rpm/installed-through-deps.list and remove the names of the packages you don't consider 'orphans'. Re-running the command to remove orphans should now show a list shorter by the packages you deleted in the file /var/lib/rpm/installed-through-deps.list.

TIP:
Occasionally, you may delete an individual file or mess up a configuration file and need to restore it. To do so, first you need to identify the package the file belonged to:

#rpm -q --whatprovides full_path_to_name_of_file

Using the full path plus the file name allows rpm to select among similarly-named files. This command is also useful if you just need to know what package provides a particular file.

To replace the missing or corrupted file, refresh the package with:

#urpmi --replacepkgs name_of_package_without_version_number

Using the name of the package less the version number allows urpmi to install the most current version.

TIP:
If you want to issue a urpmi command while another instance of urpmi is already running (and locking the rpm database), add the -wait argument and the new command will wait until the database is free before it runs.

TIP:
Place the following in your .bashrc to create and alias:

alias whatprovides="rpm -q --whatprovides `whereis %0`"


This allows you to not have to remember the long command, and simply do this:

$whatprovides file_name

TIP:
If you compile software and get messages that files are missing, you can find them with:

$urpmf missing_filename



Comments

Popular posts from this blog

DOS4GW.EXE Version 2.01a and Alternative DOS Extenders

DOS4GW.EXE The Tenberry DOS extender DOS4GW.EXE was used by many early DOS games. I still enjoy playing many of these games and DOS4GW.EXE is usable with DOSBox , so they can be played on Linux. However, the version of DOS4GW.EXE that was included with the game was whatever was current at the time. The most recent version that includes many bugfixes that possibly affected the games when used with DOSBox have been fixed in the latest version, 2.01a. It's not free at US$49, but you can downloaded it here . Simply substitute it for whatever version of DOS4GW.EXE your game provided and enjoy the bug-fixed goodness. Tenberry also makes a "high-performance" "pro" version of DOS4GW.EXE, but it costs $300. I think that they could sell quite a few of these to hobby users (since, you know, DOS is dead) for US$5. Open Souce to the Rescue There are better performing, free and Open Source alternatives available and worth a look. DPMI Explained Let's unders...

Return to Castle Wolfenstein for Modern Linux

Return to Castle Wolfenstein is a first-person shooter originally released on November 19, 2001. The game, like many other classic games, is available at GOG.com and costs only US$5.99. iortcw for Linux Don't bother with old and crusty Linux binaries offered by idsoft; they are problematic and it's painful to use them on a modern Linux. Fortunately for us, there are more modern GPL-licensed Linux binaries available for 32- and 64-bit systems as well as high resolution textures packages. The project at GitHub provides source code that can also be compiled for MS Windows using MinGW. iortcw for Windows and Mac You can download pre-compiled binaries for 32- and 64-bit Linux, MS Windows and Mac from here . Let's put our files in /usr/local/games/rtcw . As root, extract the downloaded .ZIP file for your architecture to  /usr/local/games/rtcw . All we are missing are the game data files. I purchased them from GOG.com. The game installer downloaded from GOG.com can be ...

Unpack those .EXE game files from GOG.com (Plus other un-packers)

I just came upon innoextract today. I have many of the wonderful games from GOG.com, some of which have native Linux Clients. Before now, I've had to use PlayOnLinux or Crossover to install these for use with WINE, then add the Linux client. InnoSetup as a way to create an installer to install the games on Windows.  Daniel Scharrer has created innoextract to allow the unpacking of those archives on a non-Windows platform. The website provides information on using innoextract , but this information from the page is very useful: GOG.com Installers GOG.com installers with a 2.x.x version number on the download page or in the filename use InnoSetup 5.5.0 and cannot be extracted by innoextract 1.2 and older. Older installers use InnoSetup 5.2.3 and usually have no version in the filename. Some GOG.com multi-part installers with version 2.1.x or higher use RAR archives (renamed to .bin) to store the game data. These files are not part of the InnoSetup installer and require...