[10:09] <ev> cjwatson: out of curiosity, why don't we use parted
[10:09] <ev> 's support for resizing hfs+ partitions in resize_use_free
[11:09] <cjwatson> ev: I don't really remember, TBH
[11:09] <cjwatson> ev: it's possible there wasn't much point because you have to disable the journal in order for that to work anyway
[11:19] <ev> oh, of course
[11:20] <ev> yet another reason I think we should pay someone to add journal support to the hfs+ driver
[16:11] <CIA-7> debian-installer: cjwatson * r1433 ubuntu/ (5 files in 2 dirs): Move to 2.6.38-8 kernels.
[16:39] <mterry> ev, hello again re: geonames stuff!
[16:39] <ev> hiya
[16:39] <ev> so I've at least made some progress
[16:41] <ev> minimal, but I've updated the import script to actually work
[16:41] <mterry> ev, oh?
[16:41] <ev> I was going to ask IS to run it with the most recent data, but that doesn't seem to fix the SF bug
[16:41] <ev> so I'll have to dig deeper
[16:41] <ev> anyway
[16:41] <ev> what's up? :)
[16:41] <mterry> ev, so I was looking at the localization issue
[16:42] <ev> oh?
[16:42] <mterry> ev, and realized that the data we want seems to be there, in the alternateNames.txt file and is even imported into an sql table
[16:42] <mterry> ev, but the geonames.py file (this is the code that runs on the server?) doesn't ever seem to look at that table for matches
[16:42] <ev> ah
[16:43] <ev> so in terms of what's run...
[16:43] <ev> geoname-modpython.py is what's actually behind /?query=
[16:43] <mterry> ev, ok.  that also doesn't seem to look at the alternate table
[16:44] <ev> that connects to sphinx which does full text searches against the geoname table
[16:44] <ev> and yes, as you suggest, it's not looking at alternateNames
[16:45] <mterry> ev, another wishlist is to sort by population
[16:45] <mterry> which also seems to be in the sql table
[16:45] <ev> yeah, we could definitely do that
[16:45] <ev> wishlists> feel free to beat me to it, the code is all there.  But if you're equally swamped, I'll endeavor to find time for it amongst the ubiquity bug fixing
[16:46] <mterry> ev, I was about to ask how busy you were  :)
[16:46] <mterry> ev, so you're saying both l18n and pop sorting are not things you have near-term time for?
[16:47] <ev> I'm saying I can try to fit them in, but I cannot make any promises, given the number of bugs milestoned for natty
[16:47] <mterry> I can talk to klattimer about it too, maybe he has some time
[16:47] <mterry> ev, understood.  I can try to dust off my sql
[16:47] <ev> heh, it's simple stuff, no stored procedures here :)
[16:48] <CIA-7> debian-installer: cjwatson * r1434 ubuntu/debian/changelog: releasing version 20101020ubuntu26
[16:48] <ev> do let me know of your progress if you pick it up or if Karl has time for it, that way I wont duplicate your work if I find some free cycles
[16:49] <ev> oh and let me know if you can't commit to trunk or if Karl has a launchpad ID that should be given permission to trunk
[18:01] <compaq17_> Can anyone help with an install problem?
[18:26] <ev> ugh, adorable:
[18:26] <ev> Apr  5 16:15:01 ubuntu in-target: Failed to fetch cdrom://Ubuntu 11.04 _Natty Narwhal_ - Beta i386 (20110404)/dists/natty/main/binary-i386/Packages  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
[18:27] <ev> (bug 751666)
[18:28] <ev> I've nearly got 739489 sorted.  It's still adding some duplicates, which I'll have to look into, but more importantly it's not stripping out partner or extras.
[20:51] <chris4585> hello! I just tried to upgrade using the beta ubuntu 11.04, and got a error message http://i.imgur.com/wEH0e.png and data loss, I'm not sure where things in my /home went to...
[20:55] <cjwatson> the message is self-explanatory, but it *really* shouldn't have caused data loss.  how did you determine that data was lost?
[20:56] <chris4585> cjwatson, hello, I read the error message and I don't think its too accurate, because 1) the HDD is working fine 2) I was using USB not a CD
[20:56] <chris4585> everything on the original install seems intact but my /home folder
[20:57] <cjwatson> well, it may not cover all the bases, but input/output error means a hardware problem
[20:57] <cjwatson> was /home a separate partition?
[20:57] <chris4585> cjwatson, no it wasn't
[20:58] <cjwatson> can you extract installer logs?  /var/log/syslog and /var/log/partman from the running installer
[20:58] <cjwatson> which partitioning option did you select?
[20:58] <chris4585> cjwatson, I don't think thats possible, I first tried from a CD, then from USB and then realized the files were missing, the logs are long gone
[20:59] <cjwatson> so you had an abortive installation from CD before this installation run, which you believe toasted the data?
[20:59] <chris4585> cjwatson, the upgrade option didn't provide a partition option
[20:59] <cjwatson> in that case, which partitioning option did you select in the CD run?
[20:59] <cjwatson> the screenshot you provided isn't an upgrade
[21:00] <cjwatson> it's a fresh install
[21:00] <chris4585> hrm... okay but I clearly selected upgrade..
[21:00] <cjwatson> oh, OK, there was an option added labelled "upgrade" - it's meant to be a fresh install but saving your data
[21:01] <cjwatson> (for future reference, you can just upgrade using update-manager)
[21:01] <chris4585> cjwatson, I see.  I would do that but my experience with upgrading that way, is not so pleasant, and on satellite connection it would be hell
[21:01] <cjwatson> ev: we seriously need to either ramp up the warnings on the upgrade option, or do some really serious QA
[21:02] <cjwatson> ev: if nothing else it absolutely must say that people should keep backups, IMO
[21:02] <chris4585> thanks for the help though, I'll just try to use a file recovery program
[21:02] <cjwatson> chris4585: I'm sorry for the data loss; I will try to make sure that we identify the problem before release
[21:02] <chris4585> cjwatson, well I agree.. I should have made backups before, but figured the upgrade option would have been safe enough
[21:02] <chris4585> most of the data I believe I can get back
[21:03] <cjwatson> upgrading over the net is very safe (it may go wrong mid-upgrade, but it's always recoverable, and data loss is vanishingly rare).  upgrading using the installer ... still needs work
[21:03] <chris4585> I have another question, while using the upgrade option, what actually happens to the /home folder? does ubiquity absolutely not touch it?
[21:04] <chris4585> cjwatson, I'll keep that in mind
[21:04] <cjwatson> that's how it's supposed to work
[21:04] <chris4585> ok, thanks for the help
[21:04] <CIA-7> partman-auto: cjwatson * r608 ubuntu/automatically_partition/reuse/do_option: fix indentation
[21:04] <cjwatson> it's meant to mount the old /, and remove everything owned by the system
[21:05] <chris4585> ah ok
[21:05] <cjwatson> (so it will lose any system-level customisations)
[21:06] <cjwatson> ev: hm, bearing in mind loss of system-level customisations, I recommend we phrase this more as "reinstall, preserving old user data" rather than "upgrade"
[21:06] <cjwatson> "No files will be deleted" is untrue as stated
[21:08] <chris4585> cjwatson, personally I like the Upgrade part, it makes sense, but possible list it as "Upgrade - preserving personal documents and files"
[21:08] <chris4585> just my 2cents
[21:09] <cjwatson> the thing is that we've worked hard to build up an understanding of an upgrade as something that preserves your customisations where possible
[21:09] <charlie-tca__> If it doesn't actually upgrade from old release to new release, might it be better to list it as "Reinstall on top" ?
[21:09] <cjwatson> (and, OK, failed sometimes, but that has definitely been the intention over all the years of Debian and Ubuntu development)
[21:10] <cjwatson> this is supposed to be a fresh install which preserves user data; I think describing it as an upgrade is going to cause confusion
[21:10] <cjwatson> I mean, I think it's a good option and should exist (and be fixed)
[21:10] <cjwatson> I just don't think it should be named the same way as something that's qualitatively different
[21:11] <chris4585> cjwatson, I agree I suppose, makes sense
[21:16] <cjwatson> actually, I think I exaggerate - that option preserves changes you've made to files owned by packages
[21:16] <cjwatson> but there are other customisations possible that don't fall into that category
[21:31] <cjwatson> I've filed bug 751904
[23:23] <CIA-7> ubiquity: superm1 * r4642 ubiquity/ (bin/oem-config-remove-gtk debian/changelog):
[23:23] <CIA-7> ubiquity: Modify oem-config-remove-gtk to look in /var/lib/dpkg/info again
[23:23] <CIA-7> ubiquity: rather than /var/lib/dpkg/info/*/ for installed packages.
[23:29] <CIA-7> ubiquity: superm1 * r4643 ubiquity/ (bin/oem-config-remove-gtk debian/changelog):
[23:29] <CIA-7> ubiquity: Remove cryptsetup after oem-config if ecryptfs is not in use.
[23:29] <CIA-7> ubiquity: Thanks Tony Espy.
[23:57] <CIA-7> ubiquity: superm1 * r4644 ubiquity/debian/changelog: releasing version 2.5.34