[00:16] <darkblue_b> hi all - anyone care to advise on a dist-upgrade?
[00:16] <darkblue_b> I had an 11.10 on a remote server, and I decided to give it a try
[00:16] <darkblue_b> apt-get update;apt-get upgrade;apt-get autoclean;reboot
[00:16] <darkblue_b> apt-get update;
[00:17] <darkblue_b> no dist-upgrade yet.. now I notice that my /etc/apt/sources.list shows precise.. I dont think that was there before
[00:17] <darkblue_b> apt-get update returns a whole bunch of "something wicked" msgs with an obviously defective URL
[00:18] <darkblue_b> though it did do something that worked, and apt-get autoclean works ok
[00:18] <darkblue_b> I was about to do the  apt-get dist-upgrade anyway.. but now I got
[00:18] <darkblue_b> .. WARNING: The following packages cannot be authenticated!
[00:18] <darkblue_b>   linux-image-3.2.0-27-generic linux-headers-3.2.0-27 linux-headers-3.2.0-27-generic linux-headers-server
[00:18] <darkblue_b>   linux-server linux-image-server
[00:19] <darkblue_b> so the new kernal isnt authenticated.. I am not that great with repo keys and all
[00:19] <pleia2> "dist-upgrade" doesn't mean it's upgrading you to the next version, it's just downloading updates to your current version, so at some point you must have told your sources.list to change to precise
[00:19] <darkblue_b> should I be very concerned ?
[00:19] <darkblue_b> pleia2: ok, I am listening
[00:20] <pleia2> you can use dist-upgrade to go to the next version, but in ubuntu if you're doing a command line upgrade you really want to use "sudo do-release-upgrade" since that catches things that just changing your sources and dist-upgrading may miss
[00:20] <darkblue_b> ah oh
[00:20] <darkblue_b> that sounds familiar - thx for that
[00:20] <pleia2> but if you've already updated a bunch of stuff to precise, it's too late ;)
[00:20] <darkblue_b> hah - its actually a very side server.. not essential .. so no panic
[00:21] <darkblue_b> so perhaps I will do this   do-release-upgrade
[00:21] <pleia2> you probably want to install (or update) the ubuntu-keyring package
[00:21] <darkblue_b> ah
[00:22] <darkblue_b> "ubuntu-keyring is already the newest version.'
[00:22] <darkblue_b> good thought though
[00:22] <pleia2> ah
[00:22] <pleia2> 3.2.0-27 is the current kernel in precise, odd that it wouldn't be validating
[00:23] <darkblue_b> odd - this is precise already !
[00:23] <darkblue_b> I am either forgetting that I did that, or I lost track of something :-)
[00:23] <pleia2> :)
[00:23] <darkblue_b> hmm so actaully I have a 12.04 and I just did the upgrade
[00:23] <darkblue_b> just this linux kernal missing auth
[00:23] <pleia2> seems like
[00:24] <darkblue_b> yeah - thx for your patience
[00:24] <pleia2> I need to run to dinner, good luck :)
[00:24] <darkblue_b> cheers pleia2
[00:48] <darkblue_b> sudo apt-get install members ## WARNING the following cannot be authenticated.. argh!
[00:48] <darkblue_b> I dont get how to get new keys for this
[00:48] <darkblue_b> :-(
[00:49] <darkblue_b> sudo apt-get source members
[00:49] <darkblue_b> ERR Something wicked happened resolving 'us.archive.ubuntu.com:http' (-5 - No address associated with hostname)
[00:49] <darkblue_b> something is not right
[00:50] <darkblue_b> why is there an http at the end
[00:50] <darkblue_b> and..
[00:50] <darkblue_b> wget: unable to resolve host address `us.archive.ubuntu.com'
[00:51] <darkblue_b> ugh - that address exists.. http://us.archive.ubuntu.com/ubuntu/pool/universe/m/members
[00:51] <darthrobot> [R: us.archive.ubuntu.com] Title: [Index of /ubuntu/pool/universe/m/members]
[00:51] <darkblue_b> d d d dang
[00:53] <darkblue_b> bad dns
[00:53] <darkblue_b> betcha
[00:53] <darkblue_b> 12.04   dns nameservers .. uuurgh
[00:55] <darkblue_b> adding line.. lalala
[00:56]  * darkblue_b tries to be cheery when faced with annoying minutia
[00:56] <darkblue_b> sorry for the noise everyone.. hopefully done soon
[22:25] <dbb> hi all - just to share back what I learned from yesterdays update.. it was the lack of dns-nameserver entry in /etc/netwrok/interfaces that caused the apt repo lookups to fail, and after they failed, the "could not authenticate" msgs for individual packages were persistant
[22:26] <dbb> so, by adding the dns entry, then apt-get update, then upgrade, then indivudual new packages, things now work as expected
[22:26] <dbb> my last mystery is why this IP address isnt shpwing up from the outside but does from the same IP block, but I dont expect help with that :-)
[22:27] <dbb> the 12.04 upgrade however, thats probably something to have in the back somewhere for random people like me :-)