wrong version of navit in the repositories ( 0.1 instead of 0.2 )
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | navit (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: navit
In the Ubuntu repositories navit is published as version 0.2, which is not true. On http://
Please rename the package "navit_
Possible solutions for the next time:
Better solution:
Remove navit via "apt-get remove navit" and "apt-get autoremove"
If not already existing, create a document called "preferences" in /etc/apt/ and fill in:
Package: navit
Pin: release o=latouche
Pin-Priority: 9999
This will set the priority of his packages to the highest level and the update-manager will not suggest the old packages anymore.
Reinstall navit and everything will work out just fine.
Thanks to Vincent (latouche.info) for his solution!
Otherwise:
Block the ubuntu repositories and remove navit via "apt-get remove navit" and "apt-get autoremove". Now reinstall navit using latouche's archive, activate the ubuntu rep again and DO NOT update navit via the update-manager anymore.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: navit 0.2.0~svn2897+
ProcVersionSign
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Sun Jun 6 14:42:12 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.utf8
SHELL=/bin/bash
SourcePackage: navit
| Antenna (antenna) wrote : | #1 |
| description: | updated |
| Antenna (antenna) wrote : | #2 |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| Wolfgang Kufner (wolfgangkufner) wrote : | #3 |
Hm
I just installed navit_0.
navit -v
is
navit 0.2.0
| Antenna (antenna) wrote : | #4 |
Hello Wolfgang, well, the current navit version contains version 0.1 plus the additional updates, which make it a pre-version of navit 0.2. So actually it's 0.2 beta and not the final release. As the navit_0.
The problem however is you can't update from the repositories to a more up-to-date version, can you?
Regards,
Simon
| Wolfgang Kufner (wolfgangkufner) wrote : | #5 |
I do not know much about version numbering, but since I was curious and looked some stuff up here is what I found:
There are two ways to number svn releases that seem to be equivalent:
e.g.:
navit_0.1.1+svn1234
navit_0.2.0~svn1234 (the tilde means less than; a package 0.2.0 would supersede it;)
The latouche archive uses 0.1.0+svn version numbers while 0.1.1 has been released.
The program internally speaks of itself as 0.2.0 (both the navit -v commandline and the about page in the GUI).
debian uses the 0.2.0~ numbering, too:
http://
I also suspect that reducing the version number is maybe not practical. Up might be the much preferred direction.
I suspect that it would be much easier to ask the maintainer of the latouche archive whether he would consider changing to the debian/ubuntu numbering.
Just my two cents.
Regards,
Wolfgang
| Antenna (antenna) wrote : | #6 |
You're right, it sure is way easier to ask Latouche, since updating or even renaming the repository package will take a looong time.
And I thought so either, when I found out why updating didn't work.
On the other hand, Latouche's solution was to change the priority of the packages and not to rename his packages, thus I thought Latouche or the navit team probably thought more about how they name their packages than the Debian/Ubuntu team did.
Guess, I should give it a try and contact him again. ;)
| Bernd Zeimetz (bzed) wrote : | #7 |
Problems with packages installed from other repositories are neither a bug in Debian nor Ubuntu.
| Changed in navit (Ubuntu): | |
| status: | New → Invalid |
Well, blocking the ubuntu repositories and removing navit via "apt-get remove navit" and "apt-get autoremove" did the job.
Just reinstall it, allow the ubuntu rep. again and just don't update navit.