[00:41] <slangasek> infinity, stgraber: there haven't been any further reports of 1017001 since flipping the switch, that I can see; it seems it may truly have been specific to users doing strange things like running mythbuntu 10.04 without updates applied.  I think we can take it off our worry list now.
[00:43] <stgraber> well, that's very good news
[01:05] <infinity> slangasek: See, and I was just about to say that I ran into it in production.
[01:06] <infinity> slangasek: And the only solution here was to install the upstart interdependant mess before proceding with the rest.
[01:06] <infinity> slangasek: That's a pretty big update-manager change, but I wonder if it wouldn't just be the right thing to do. :/
[01:10] <infinity> It's a short list: upstart initramfs-tools initramfs-tools-bin udev initscripts ifupdown mountall plymouth
[01:10] <infinity> Upgrading those first seems to make the rest of the process a bit more resilient.
[01:11] <infinity> (And yeah, I literally JUST ran into this on my powerpc/lucid machine when I upgraded it to precise, and it wasn't mythbuntu)
[01:11] <infinity> It was, however, a debootstrap + ubuntu-desktop by-hand install, not something from lucid media.
[01:12] <stgraber> and I guess in your case, was fully up to date before the dist-upgrade
[01:13] <infinity> stgraber: Yeah, I updated it to -updates before doing the upgrade, cause I didn't want problems. :P
[01:13] <infinity> All of those packages are Priority:required, so it wouldn't (in theory) do any harm to just force an install of all of them before the rest of the upgrade.
[01:14] <infinity> Given that if they're not installed, we really think they should be.
[01:16] <xnox> infinity: does this mean your powerpc machine is now back alive and operational?
[01:16]  * xnox \0/
[01:16] <infinity> xnox: My PowerStation is on and being a wind-tunnel again.
[01:16] <infinity> xnox: It's not my only PPC machine. :P
[01:16] <xnox> =)))))) nice
[01:16] <xnox> show off
[01:17]  * jocarter wonders if infinity, xnox and stgraber ever stop working
[01:17] <stgraber> infinity: I can't remember if the dist-upgrader actually has a feature to force a given list of packages to upgrade before doing the main upgrade
[01:17] <infinity> jocarter: For about 28 minutes on Thursday afternoons.
[01:17] <infinity> stgraber: I'm not sure either, though it seems like a sane thing to be able to do to influence things a bit.
[01:17] <stgraber> infinity: I know it has a list of packages to ensure are installed post-upgrade and a list of stuff to cleanup
[01:17] <jocarter> infinity: heh
[01:17] <stgraber> agreed, if it doesn't support it, it should
[01:18] <xnox> jocarter: i'm not working. i'm just breaking archive by uploading incompatible versions of mumble ;-)
[01:18] <stgraber> jocarter: well, at least for me there's a pretty big difference between talking in #ubuntu-release and working ;)
[01:19] <stgraber> xnox: bah, who uses quantal anyway? :)
[01:20] <infinity> stgraber: Hrm, there's [PreRequists](sic) in the .cfg, but that's to install from $old_release, not $new_release.
[01:22] <stgraber> infinity: I also suppose we want the dist-upgrader to use the backported apt to install these packages?
[01:23] <infinity> stgraber: Possibly.  They'll end up depending on a newer dpkg and libc anyway, I imagine.  I'm not sure apt itself matters much for such a small set.
[01:23] <infinity> stgraber: But, since the whole thing operates with the release-upgrader-python-apt, the point seems moot.
[01:27] <infinity> stgraber: Oh, hrm.  Prereqs is actually entirely unclever.  It just uses a separate sources.list and then installs what you asked for.  I wonder if we couldn't just call back into that exact same method for a PreInstall or something that runs between PreReq and Upgrade.
[01:28] <infinity> Or UpgradeFirst might be a better name for it, so it's obvious it's something you can't go back from.
[01:28] <infinity> But whatever.
[01:29] <infinity> Still, this is all a pretty huge potential change for code that's been heavily tested without it. :/
[01:30] <infinity> And we have exactly one reliable reproducer for the bug, which is about as helpful as using a puppy as a television remote control.
[01:30] <xnox> don't be cruel to animals!
[01:31] <infinity> Don't worry, the puppy thinks it's a fun game.  The only harm done is to your sanity when the channel doesn't change, no matter how you rub his tummy.
[01:32]  * xnox =)
[01:32] <xnox> infinity: i think you should be on Ubuntu TV design team =)
[01:33] <xnox> and fix puppy remotes onces and for all!
[01:44]  * infinity reboots to finish the upgrade and crosses his fingers.
[01:45] <infinity> Hrm.  "Not a valid ELF image".
[01:46] <infinity> Thanks, yaboot.
[01:46] <infinity> That's probably my fault, though.  Cobbled-together cross-grade from YDL to Debian to Ubuntu.
[01:47] <xnox> it's sad to see installs outliving distributions
[01:49] <infinity> Ouch, and the old kernel explodes with udev having a sad.
[01:49] <infinity> *sigh*
[01:49] <infinity> This'll be fun to recover.
[01:50] <infinity> For some value of "fun" that involves a Debian CD and some luck.
[02:04] <infinity> Ah-ha, just needed a newer version of yaboot.
[02:04] <infinity> The upgrade really should update that. :/
[02:05] <infinity> Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-powerpc64-smp ppc64)
[02:05] <infinity> I win!
[02:06] <infinity> Well, I kinda win.  If X wasn't now spinning at 100% and not drawing pretty pictures...
[02:15] <slangasek> infinity: oh, huh.  was it on a fully-updated system?
[02:15] <slangasek> ah, you say it was
[02:16] <infinity> ioctl(7, 0x20006444, 0)                 = -1 EBUSY (Device or resource busy)
[02:16] <infinity> Really, X?  That's a spiffy infinity loop.
[02:16] <infinity> infinite, too.
[02:17] <infinity> Seems my nick has broken my ability to type "infinite".
[02:49] <infinity> Oh hey, finally.
[02:49] <infinity> Oh, armel is still building.  Drat.
[02:52] <infinity> Nobody worry about that linux build in quantal-proposed, I've got a d-i upload queued later to go with it.
[11:56] <phillw> hot off the press bug 1041532
[11:56] <ubot2`> Launchpad bug 1041532 in ubiquity "A update process in Ubiquity caused it to crash" [Undecided,New] https://launchpad.net/bugs/1041532
[11:59] <smartboyhw> Hi. Did phillw give you the bug that I just reported?
[12:00] <phillw> smartboyhw: yes I did
[12:04] <smartboyhw> Thanks phillw
[18:00] <phillw> any release team still awake?
[18:02] <phillw> I've suggested Ubiquity... http://pastebin.com/Z0wCgj0B
[18:03] <tumbleweed> the fontocnfig warning is benign
[18:04] <phillw> tumbleweed: so, what more data do you guys need?
[18:04] <tumbleweed> no idea wthat the problem is, but this isn't really a support channel
[18:04] <phillw> he he.. it is the release channel, and this is a 12.10 issue :P
[18:05] <tumbleweed> #ubuntu+1
[18:05] <phillw> okies, I'll head there, thanks
[18:11] <xnox> tumbleweed: known problem new fontconfig became too 'chatty' and picky what it believes are sane font configs shipped with fonts, mostly harmless.
[18:11] <tumbleweed> yeah. doesn't stop machines from booting, though
[18:12] <xnox> tumbleweed: yeah, but rather annoying to see them on every application launch from the terminal
[18:12] <tumbleweed> that's presumably a broken X of some sort