To maintain network compatibility, please update warsow to its latest stable release.
The given download page only cites "Old version: Warsow 2.1", but this reveals itself to be 2.1.2 . Again, no release information to justify the update. Beware 444Mb tarball. No particular maintainer evident, so assigning this globally.
Assignee: bugsquad => pkg-bugs
*** Bug 31606 has been marked as a duplicate of this bug. ***
CC: (none) => linux
It might be good to update this old package for Mageia 9 (MGA9).
Main warsow-2.1-4.mga9.nonfree is up-to-date as the real source code is warsow_21_sdk.tar.gz from: https://warsow.net/warsow_21_sdk.tar.gz But the one's which should be only updated is warsow-data-2.1-4.mga9.nonfree with source code: https://warsow.net/warsow-2.1.2.tar.gz
CC: (none) => geiger.david68210
Many thanks you for your fast work and released updates. There seems to be some depency problems - maybe something needs to adjusted. When i try to install warsow, it still tries to download and install "warsow-data-2.1-4.mga9.nonfree...." but there is "warsow-data-2.1.2-1.mga9.nonfree.noarch.rpm" on the servers and it stops the download because of missing file on the server (want to download the old/not existing file).
Tested with "uprmi warsow"
Can not confirm psycas problem. Everything installs fine on an up-to-date cauldron system: $ LANG=C urpmi warsow Password: To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Nonfree Release") warsow 2.1 4.mga9.nonfr> x86_64 warsow-data 2.1.2 1.mga9.nonfr> noarch 438MB of additional disk space will be used. 427MB of packages will be retrieved. Proceed with the installation of the 2 packages? (Y/n) y http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/media/nonfree/release/warsow-2.1-4.mga9.nonfree.x86_64.rpm http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/media/nonfree/release/warsow-data-2.1.2-1.mga9.nonfree.noarch.rpm installing warsow-data-2.1.2-1.mga9.nonfree.noarch.rpm warsow-2.1-4.mga9.nonfree.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ########################################################################### 1/2: warsow ########################################################################### 2/2: warsow-data ###########################################################################
Ok. It works. Made an clean Mageia 9 Beta 1 install and it downloads and installs now. My other VM might be a bit broken. So it could be marked as "fixed". Thank you :)
Hm. Seems to be a problem with the princeton mirror. My new Mageia install used an other one. -- [root@localhost nutzer]# urpmi warsow Um die Abhängigkeiten zu erfüllen, werden die folgenden Pakete installiert: Paket Version Release Arch (Medium »Nonfree Release (distrib11)«) warsow 2.1 4.mga9.nonfr> x86_64 warsow-data 2.1 4.mga9.nonfr> noarch 438MB zusätzlicher Speicherplatz werden benötigt. 427MB an Paketen werden geholt. Fortfahren mit der Installation der 2 Pakete? (J/n) j http://mirror.math.princeton.edu/pub/mageia/distrib/cauldron/x86_64/media/nonfree/release/warsow-data-2.1-4.mga9.nonfree.noarch.rpm http://mirror.math.princeton.edu/pub/mageia/distrib/cauldron/x86_64/media/nonfree/release/warsow-2.1-4.mga9.nonfree.x86_64.rpm … Holen fehlgeschlagen: wget Fehler: Beendet mit 8 http://mirror.math.princeton.edu/pub/mageia/distrib/cauldron/i586/media/nonfree/release/warsow-data-2.1-4.mga9.nonfree.noarch.rpm … Holen fehlgeschlagen: wget Fehler: Beendet mit 8 Installation fehlgeschlagen, einige Dateien fehlen: http://mirror.math.princeton.edu/pub/mageia/distrib/cauldron/i586/media/nonfree/release/warsow-data-2.1-4.mga9.nonfree.noarch.rpm http://mirror.math.princeton.edu/pub/mageia/distrib/cauldron/x86_64/media/nonfree/release/warsow-2.1-4.mga9.nonfree.x86_64.rpm Sie sollten Ihre urpmi-Datenbank aktualisieren.
Issue an "urpmi.update -a" to update your repository list.
Now it works. Normaly i use "urpmi --auto-update" to update the repository lists and update the installed packages before installing new one. Now its finaly ok.
As both packages are already in nonfree-release...closing as fixed.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED