=== ionutjula is now known as fdd_ [05:13] nijaba: good question [08:34] nijaba: it will take about a week I guess [08:34] mdke: really? why is it so long? [08:40] mdke: anything we can do to speed it up? [08:41] nijaba: not really, it just takes a lot of work [08:42] mdke: and can I help in the work? [08:42] nijaba: maybe it can be done by the end of the weekend, then a few days to upload it [08:42] nijaba: no, I don't think so - it's a one person job [08:43] mdke: okay, so I should wish you good luck then :) sorry for the disturbance [08:43] thanks for the offer though [12:11] New bug: #221819 in ubuntu-doc "UbuntuHashes page does not have hashes for 8.04" [Undecided,New] https://launchpad.net/bugs/221819 [13:35] New bug: #220889 in ubuntu-docs "wrong 8.04 codename in Korean start page" [Undecided,New] https://launchpad.net/bugs/220889 === po1ter is now known as polter === fdd-0 is now known as fdd [16:10] !help core [16:10] Sorry, I don't know anything about help core - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi [16:10] !help [16:10] I am ubotu, all-knowing infobot. You can browse my brain at http://ubotu.ubuntu-nl.org/factoids.cgi - Usage info: http://wiki.ubuntu.com/UbuntuBots [17:02] Hello, may I suggest something to add to the upgrade notes? [17:08] Anyway, in case someone reads this later on, I'd like to know what is the recommended way to update a Ubuntu desktop "remotely", via a ssh session, with no GUI. Would the instructions for upgrading a Ubuntu server apply? [17:14] sudo do-release-upgrade [17:20] OK, it would help to add a one-liner confirming this on the web page. Thank you. [17:22] it's on http://www.ubuntu.com/getubuntu/upgrading under "Network upgrade for Ubuntu servers" [17:23] Yes, "for Ubuntu Servers" but I'm asking whether this procedure is also valid for Ubuntu "Desktops". [17:24] what the sudo do-release upgrade? [17:24] Yes [17:25] it works for desktop too [17:26] the only reason they recommend using update-manager for the desktop is because its available [17:27] Good, that's what I'm suggesting you confirm in the web page. In my case, I want to remotely upgrade my mom's PC and I was looking for the recommended way to do it via ssh. [17:28] I see your point [17:30] I they basically do the same thing except one uses a gui and one doesn't [17:30] you will get a warning when upgrading with ssh [17:31] That's the point. My mom lives abroad and I don't want to upgrade her machine using a GUI. Just addning a note saying that do-release works for the desktop edition as well would help. [17:32] A harmless warning? [17:33] it just warns that you ssh session do end prematurely and opens up another ssh connection just in case [17:34] I upgraded a server that way and it never did disconnect so..... [17:35] OK, whatever. I just wanted to suggest to make an explicit note available on the upgrade page talking about this and saying what the recommended way to do it is. [17:39] I suggest running it inside screen, in case you do get disconnected, if you're going over SSH [17:40] That's a good suggestion (one more line to add to the web page :-)