=== mceier_ is now known as mceier [15:00] Anyone know if you can update to the Dev version of 19.10 now? [15:06] bittin: you *can*. Just be aware that it is VERY early in the cycle. If you know what you are doing, then do it -- preferrably in a TEST machine, at least initially. [15:07] hggdh: alright how do i do then? [15:08] bittin: the usual caveats apply: your machine may burst in flames, kittens may die, etc. In other words: assume some critical issue may pop up, and plan accordingly [15:09] bittin: (1) verify /etc/update-manager/release-upgrades is set to 'normal'; if not, do so; [15:10] bittin: (2) close all currently-running programs, open a terminal, and run 'sudo do-release-upgrade -d' [15:10] bittin: actually, (0) make a backup of everything you consider important in your machine [15:14] bittin: all the above assumes you are running a clean version of Ubuntu. No PPAs, no non-ubuntu programs/products installed, up-to-date. If there are (any of them), YMMV a lot. [15:25] eoan isn't in http://changelogs.ubuntu.com/meta-release-development yet, so i don't think do-release-upgrade knows about it [15:25] this early in the cycle you'd probably need to edit sources.list and dist-upgrade [15:25] dax: does not seem so [15:27] its raining cosmic to dingo upgrade fails in -announce [15:27] see bug #1825420 also [15:27] bug 1825420 in linux (Ubuntu) "package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned" [High,Confirmed] https://launchpad.net/bugs/1825420 [15:27] dax: i tried not sure if i did anything wrong: https://pastebin.com/hPSCG7vT [15:28] bittin: it's spelled eoan [15:28] (and some of those repositories may not exist yet, since eoan is so new) [15:29] i know hggdh already mentioned it, but just to emphasize: it's *extremely* early in the eoan cycle, and stuff is liable to be missing or broken for months [15:30] dax: thanks, updating 405 packages now [15:30] good luck :) [15:31] thanks [15:32] bittin: are you installing 19.10 for fun or want to help bug out? [15:32] lotuspsychje: for fun but will report if i found bugs [15:33] bittin: hence my question, if you want to help bug out we reccomend using clean dailys and not upgrades. this way you wont give extra seeking work to the developers [15:36] lotuspsychje: well i have a stable install on another ssd in case something really horrible happends [15:37] is it also a 19.10 bittin ? [15:37] lotuspsychje: nope 19.04 [15:40] !info linux-image-generic [15:40] linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 5.0.0.13.14 (eoan), package size 2 kB, installed size 15 kB [15:40] Listening too http://ubuntupodcast.org/2019/05/02/s12e04-ant-attack/ and updating to 19.10 now [15:41] bittin: let us know if your upgrade went well ok, as its same kernel as the cosmic to dingo bug [15:44] lotuspsychje: will do gonna listen to todays Ubuntu Podcast episode first and do a reboot [15:51] gonna reboot now wish me luck [15:54] https://i.imgur.com/PN61p7m.png [15:54] lookin good [15:54] it booted [15:54] thats a good start :) [15:55] bittin: how about your sources list and kernel version? [15:56] kernel 5.0.0-14 [15:56] sounds good [15:56] and sources.list seems fine [16:00] thanks for the help and cya around [16:15] :) === viv`d is now known as vivid