I've made sure that the first Dapper point release will have this fix on
top of the XFS validation changes I'd already made.
ubiquity (1.0.13) dapper-updates; urgency=low
* Don't require entering a full name (see
http://www.hermann-uwe.de/blog/os-install-experiences-part-4-ubuntu).
* GTK
ubiquity (1.1.3) edgy; urgency=low
* Fix typoed variable name while raising InstallStepError.
* Rename Partman component to PartmanAuto to allow for a future all-in-one
partman component
(https://launchpad.net/distros/ubuntu/+spec/ubiquity-advanced-partitioner).
* When an error occur
Damn, wrong bug. Sorry!
** Changed in: user-setup (Ubuntu)
Sourcepackagename: user-setup => ubiquity
--
When installing with /boot as an XFS partition, the installer crashes
https://launchpad.net/bugs/53642
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
chpasswd: line 1: unknown user shadow
That username is reserved for use by the system; I'm afraid you have to
pick a different one. Bug 50036 notes that the installer should have
warned you about this.
** Changed in: ubiquity (Ubuntu)
Sourcepackagename: ubiquity => user-setup
--
When installing
Just a sidenote, it's normally best to use a filesystem such as Ext2 for
/boot rather than anything else.
--
When installing with /boot as an XFS partition, the installer crashes
https://launchpad.net/bugs/53642
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
The immediate crash you encountered is already fixed in my working tree
for ubiquity 1.1.3:
* Fix typoed variable name while raising InstallStepError.
However, it does seem that the validation I tried to add for XFS doesn't
work, and I think I might see why (fstype is None at that point). The
q
