Error repeatedly on Ubuntu upgrade to 11.04 beta (error in Version string 'wx-11.3.1-1': version number does not start with digit)

Bug #753970 reported by sl45sms
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Software Updater
Invalid
Undecided
Unassigned
amaya (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On upgrade from 10.10 to 11.04 Beta 1 the following error is repeatedly shown on terminal:

error in Version string 'wx-11.3.1-1': version number does not start with digit

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

hello
Can you please run in a terminal

sudo apt-get clean

update-manager -d

thanks
Fabio

Changed in ubuntu:
status: New → Incomplete
tags: added: maverick2natty
removed: 11.04
Revision history for this message
sl45sms (sl45sms) wrote :

Sorry, my fault, i think the error comes not from upgrade but from package amaya

I'm on Natty Narwhal and on update terminal i get the folowing:

...............
dpkg: warning: parsing file '/var/lib/dpkg/status' near line 50170 package 'amaya':
 error in Version string 'wx-11.3.1-1': version number does not start with digit
dpkg: warning: parsing file '/var/lib/dpkg/available' near line 51735 package 'amaya':
 error in Version string 'wx-11.3.1-1': version number does not start with digit
..............

affects: ubuntu → amaya (Ubuntu)
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello
I cannot see amaya in Natty's repository using synaptic or dpkg -S
Then the problem is why update-manager consider this package as upgradeable ?
I mark as affecting update-manager too.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

@sl45sms
to fix your problem I think you have to remove the amaya-data and amaya-doc and reinstall it from the w3c site.
Sorry
Fabio

Changed in amaya (Ubuntu):
status: Incomplete → Confirmed
Changed in update-manager:
status: New → Confirmed
Revision history for this message
sl45sms (sl45sms) wrote :

After removing amaya and upgrade the error is still there

error in Version string 'wx-11.3.1-1': version number does not start with digit

Revision history for this message
sl45sms (sl45sms) wrote :

Here is the contents for package amaya on /var/lib/dpkg/status

Package: amaya
Status: deinstall ok config-files
Priority: optional
Section: web
Installed-Size: 52284
Maintainer: Laurent Carcone <email address hidden>
Architecture: i386
Version: wx-11.3.1-1
Config-Version: wx-11.3.1-1
Depends: libatk1.0-0 (>= 1.20.0), libc6 (>= 2.4), libexpat1 (>= 1.95.8), libfreetype6 (>= 2.3.5), libgcc1 (>= 1:4.1.1-21), libglib2.0-0 (>= 2.16.0), libgtk2.0-0 (>= 2.12.0), libpango1.0-0 (>= 1.20.5), libraptor1 (>= 1.4.16), libsm6, libssl0.9.8 (>= 0.9.8f-1), libstdc++6 (>= 4.2.1-4), libx11-6, libxext6, libxinerama1, zlib1g (>= 1:1.2.3.3.dfsg-1)
Description: XHTML, MathML, and SVG editor from w3.org
 Amaya is a Web editor, i.e. a tool used to create and update documents
 directly on the Web. Browsing features are seamlessly integrated with
 the editing and remote access features in a uniform environment.
 Amaya is based on the Thot toolkit developed at INRIA.

Remove the above manually fix the problem.
I believe update-manager don't auto remove the package because the wrong version string

Revision history for this message
Andreas Moog (ampelbein) wrote :

This isn't a bug in update-manager and certainly not in the official amaya version that is in the repositories. You downloaded a package from amaya's website and that package has a invalid version number. Unofficial packages are unsupported in ubuntu.

Changed in update-manager:
status: Confirmed → Invalid
Changed in amaya (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
reagle (joseph.reagle) wrote :

I think the problem is that there is no official version in natty. I certainly can't find it.

Revision history for this message
Andreas Moog (ampelbein) wrote :

Correct, it has been removed from the archive in the jaunty cycle, see bug #355013. And as I said, the package on the amaya homepage has a non-valid version string. You should complain to the programmers and have them fix it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.