ubiquity release name not set correctly

Bug #507615 reported by Claude Heiland-Allen on 2010-01-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Puredyne Live
Medium
danstowell

Bug Description

installing latest iso twice in a row in virtualbox, it seems there are two minor issues:

1. ubiquity says installed previously-ubiquity-installed Puredyne is Ubuntu 9.10 (9.10)
2. ubiquity says it will replace that installation with (empty string)

see attached screenshot

Aymeric Mansoux (aymeric) wrote :

1. I don't think we can fix that. After all it is Ubuntu that is installed. I tried to change the LSB info (from which ubiquity and co reads their stuff) to Puredyne during the LABoral sprint and ubiquity was not working anymore. It was trying to download packages for a distro called Puredyne on the Ubuntu mirrors, instead of downloading the Ubuntu deb packages ...

2. maybe incomplete ubiquity config?

Changed in puredyne-live:
status: New → Confirmed
importance: Undecided → Medium
danstowell (danstowell) wrote :

Clue: I grepped for the string shown in the screenshot, "Where do you want to put" - in our case followed by a blank space - and found the string "Where do you want to put Ubuntu?" given as a translateable string in the xml file /usr/share/ubiquity/gtk/stepPartAuto.ui - so it means that ubiq is doing a replace on the string "Ubuntu" somewhere?

Changed in puredyne-live:
milestone: none → 10.04
danstowell (danstowell) wrote :

Found it. I've committed a patch for /usr/lib/ubiquity/ubiquity/misc.py which sets the name to us

Changed in puredyne-live:
assignee: nobody → danstowell (danstowell)
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers