=== superm1|away is now known as superm1
[07:07] <superm1> is there any particular reason that a depmod being launched from a script in ubiquity wouldn't be updating modules.dep?  I can't seem to identify any reason for it not getting updated because i can manually run it in the chroot afterward just fine
[07:10] <superm1> er well i suppose that would be caused by /usr/lib/ubiquity/compat/depmod ...
[07:21] <superm1> i wasn't catching it because it's added to the PATH so early
[08:01] <CIA-50> ubiquity: superm1 * r2840 ubiquity/ (debian/changelog scripts/mythbuntu/apply-drivers): run the /real/ depmod once when installing proprietary drivers on the mythbuntu frontend
[08:39] <CIA-50> ubiquity: superm1 * r2841 ubiquity/ (debian/changelog ubiquity/frontend/mythbuntu_ui.py): Restrict custom remotes from mythbuntu install
=== superm1 is now known as superm1|away
[14:30] <CIA-50> ubiquity: cjwatson * r2842 ubiquity/ (debian/changelog ubiquity/misc.py): Improve logging of exception tracebacks in find_in_os_prober.
[14:40] <CIA-50> ubiquity: cjwatson * r2843 ubiquity/ (debian/changelog ubiquity/misc.py):
[14:40] <CIA-50> ubiquity: Just log an informative message when a device isn't found in os-prober's
[14:40] <CIA-50> ubiquity: output, not a traceback.
=== superm1|away is now known as superm1