[00:07] <bjf> kamal, i'm including an ACK for you on that patch
[00:08] <kamal> bjf, yes please
[00:11] <bjf> dannf, i'm going to adjust the commit subject just a little (drop the [3-13-stable only])
[00:11] <dannf> bjf: oh, sure
[00:12] <kamal> bjf, fyi here's the version I applied to 3.13-stable http://kernel.ubuntu.com/git/ubuntu/linux.git/commit/?h=linux-3.13.y-queue&id=eef5d05f530ba16df8f758f6ae72f62e4ac7a503
[02:57] <bjf> infinity, dannf trusty uploaded
[16:15] <awe> cking, around?
[16:15] <cking> awe, just about
[16:16] <awe> so I just had a recent utopic kernel update land on my macair, and it nuked by rEFInd install...
[16:16] <awe> thankfully I was able to boot, by powering on with the Option key pressed
[16:17] <awe> this is the first time I've ever had an Ubuntu update nuke it
[16:17] <awe> ( it's usually the other way around )
[16:17] <awe> just wondering who I should bug about this?
[16:17] <awe> ( no pun intended )
[16:17] <awe> I'm also gonna shoot an email to rodsmith
[16:18] <awe> ( rEFInd maintainer )
[16:18] <cking> awe, yeah, I've got zero know-how with rEFInd
[16:19] <awe> I thought you wuz the EFI king?
[16:19] <awe> ;)
[16:19] <awe> np
[16:20] <awe> maybe I'll see what rod has to say, then come back and ask for more help
[16:20] <cking> awe, I try to keep away from macs
[16:20] <awe> why, cause you love where lennovo is these days?
[16:20] <awe> ;/
[16:20] <cking> awe, heh, I'm more into file system and ACPI at the moment
[16:20] <awe> I try and stay away from dell ( for obvious reasons )
[16:20] <awe> ( mostly personal )
[16:20] <rtg> awe, I think there was a mishap with a grub update this morning. perhaps cjwatson could elaborate.
[16:20] <awe> ah...
[16:21] <awe> that sounds like a smoking gun for sure
[16:21] <rtg> rbasak noticed it
[16:21] <awe> thanks rtg
[16:24] <rtg> awe, if you do another update then you ought to get another grub package (if that was indeed your problem)
[16:25] <awe> ok
[16:31] <rbasak> awe: thank you for the report. Please let us know if this did fix your issue. I wasn't sure how many people were affected, but if it's been picked up this quickly perhaps we should adjust SRU processes to make sure it can't happen again.
[16:31] <rbasak> (since at the moment it depends on SRU team members knowing about it)
[16:32] <awe> trying now...
[16:33] <awe> be right back ( hopefully )
[16:43] <awe> rbasak, so I updated grub to 0.97-29ubuntu66; rebooted and rEFInd still doesn't load.... I need to power up with the Option key pressed in order to trigger EFI Boot
[16:52] <apw> awe, that doesn't sounds like a kernel issue though, hmmm
[16:54] <awe> apw, rtg mentioned earlier that there was a grub mishap this morning, and rbasak had asked it that cleared it up
[16:54] <awe> apw, totally agree it's not a kernel issue
[16:54] <awe> just originally thought it might be related
[16:55] <rbasak> awe: thanks. I'm not particularly familiar with the signed grub stuff, just that I know that they need to be updated in lockstep.
[16:55] <awe> np
[16:55] <rbasak> Are we absolutely sure that your failure isn't a consequence of the failure this morning?
[16:56] <awe> no idea
[16:56] <awe> I applied an update, and didn't pay too much attention to the involved packages, other than there was kernel update included.  Things failed on the reboot
[16:57] <rbasak> smb: you're probably gone for the day but maybe you can look into this with awe in the morning please? My concern is that we released grub2 to -updates this morning without doing grub2-signed, until cjwatson fixed it later on after I noticed. I'm wondering what impact this might be having on users.
[16:58] <smb> rbasak, I am still here... well if you are not careful apt-get dist-upgrade will put the signed part on the "will be removed" list
[16:58] <rbasak> smb: ah, so so awe, do you have the package grub-efi-amd64-signed installed still? Or is it removed?
[16:59] <smb> update-manager warns about partial upgrade but command line is quite easy to miss
[16:59] <awe> nope
[16:59] <awe> and there was no error from update-manager
[16:59] <rbasak> Nope you have it installed still, or nope it's not there? :)
[16:59] <awe> nope it's not there
[17:00] <rbasak> Ah, that'll be it. Please install it.
[17:00] <awe> k
[17:00] <rbasak> Hopefully that'll resolve the problem.
[17:01] <awe> so before I pull the trigger, it says it'll install: grub-efi-amd64 grub-efi-amd64-signed grub2-common
[17:01] <awe> and remove: grub
[17:01] <awe> is that correct?
[17:01] <rbasak> Hmm
[17:01] <rbasak> I'm not sure.
[17:01] <rbasak> So please don't do it on my account. We're right on the edge of my knowledge, sorry.
[17:01] <awe> np
[17:02] <smb> at least that seems to be missing on my side
[17:02] <smb> grub-common, grub-efi-amd64, grub-efi-amd64-bin, grub-efi-amd64-signed, and grub2-common is what is installed here
[17:02] <awe> k
[17:02] <rbasak> awe: if you look at /var/log/apt/history.log, can you see what was removed this morning?
[17:03] <awe> smb, when someone earlier mentioned a mishap with grub
[17:03] <awe> I ran an apt-get install grub
[17:03] <awe> thinking I was updating something
[17:03] <awe> I'll go ahead an apply this
[17:03] <rbasak> awe: you should be able to check history.log and figure out exactly what you need to undo from there.
[17:03] <awe> k
[17:03] <rbasak> You basically want the same set of packages installed that you had yesterday ;)
[17:04] <awe> and where do I find history.log?
[17:04] <smb> awe, ok, yeah. might be even grub is grub 1
[17:04] <rbasak> /var/log/apt/history.log
[17:05] <smb> at least grub-efi-amd64 seems to conflict by purpose with grub
[17:06] <smb> hm now... but anyway... I think its ok
[17:06] <smb> now/no
[17:07] <smb> Oh bah. yes it is. To much text on my terminal for the hour. So grub is grub 0.97...
[17:08] <awe> yea, I think I'll be OK after this.  lemme try again
[17:08] <rbasak> I need to go.
[17:08] <awe> thanks for your help rbasak!
[17:08] <rbasak> awe: np, sorry for the issues.
[17:11] <smb> awe being back might be a good sign
[17:11] <awe> nah
[17:11] <awe> I think I might need to 're-bless' rEFInd from OS X
[17:12] <awe> I'll try and follow up with rodsmith
[17:12] <awe> I can boot w/the Option key pressed... and that allows me to start the EFI Boot
[17:12] <smb> Ok, unfortunately I would not be of much help with anything that says Mac on it
[17:12] <awe> np
[17:13] <awe> but something definitely broke, so it'd be nice to find out what, so we can prevent in the future
[17:13] <awe> ( or at least understand it )
[17:15] <smb> Yeah, as far as I got it its the signed versions problem (independent package but version depending). So need more care when uploading. 
[17:15] <smb> Otherwise it requires paying close attention on what the upgrade dialogue tells you