Skip to main content

Configuring urpmi-proxy for Mageia


Not much has been mentioned about urpmi-proxy for Mageia. In theory, urpmi-proxy works as a local proxy for a Mageia repository. You set it as the source repository for all your machines and it downloads and distributes only what packages you need.

For the most part, little configuration is needed "out of the box". It is configured by default to use the existing repositories that are already configured on the host/server machine but as pointed out, this creates a recursive loop should you update the server itself. The Wiki docs explain how to circumvent this issue.

There are other package management systems available from Mageia, notably dnf which will become the standard system only after the Mageia build system, dependent on urpmi, can be translated to dnf. 

Configuring the Server

Simply invoke

$ sudo urpmi urpmi-proxy

And this will also install the apache webserver, which is used to serve the files to your other machines. Then restart Apache.

$ sudo systemctl restart httpd.service

This will configure your urpmi-proxy server. There are other configuration options that can be modified in the well-commented configuration file. It can now serve files for any release version and architecture that is available from the server you selected from the database.

Set apache to start at every boot and then start it.

$ sudo chkconfig httpd on
$ sudo systemctl start httpd.service


Configure the Client Machine

You need to remove the urpmi source already configured for the client machine by invoking

$ sudo urpmi.removemedia -a

And point it at your urpmi-proxy server with

$ sudo urpmi.addmedia --distrib http://my_server.com/mageia/distrib/9/x86_64

You can use your urpmi-proxy server to serve any version and any architecture by specifying the appropriate path in the command above.

My server is an older i586 box that has ample disk storage space and works fine for this purpose. I have not configured it to update itself with urpmi-proxy, so there is no recursion issue, but the Wiki docs explain how to address that.

Adding A Local Repository

I have a few self-made rpm files and some commercial applications. It would be nice to have these available to my network of Linux computers. Since my server install is slightly different (the i586 server I use does not use urpmi-proxy), I must create the expected file hierarchy from scratch, using the name extra as shown in the Wiki example.

$ sudo mkdir -p /var/lib/urpmi-proxy/repository/distrib/9/x86_64/media/extra/release/

Next, I populated the /release directory with files and created the index using

$ sudo genhdlist2 --allow-empty-media --no-bad-rpm --xml-info --clean /var/lib/urpmi-proxy/repository/distrib/9/x86_64/media/extra/release/

Finally, edit the media.cfg file to add

[extra/release]
hdlist=hdlist_extra_release.cz
name=Extra Release
media_type=release

and place the modified file in /var/lib/urpmi-proxy/repository/distrib/9/x86_64/media/media_info/

However, the Wiki is not clear as to where the media.cfg file can be found on the system. Add it to /etc/urpmi/mediacfg.d/Official-9-x86_64/media.cfg.

RESOURCES

HOWTO proxy rpm using urpmi-proxy, Mageia Forum

Urpmi-proxy, Mageia Wiki

Urpmi, Mageia Wiki

Mageia mirrors database

Add Special Repos to Mageia


Labels:

Comments

Post a Comment

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...
1 comment
Read more

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 ...
1 comment
Read more

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...
1 comment
Read more