| lotuspsychje | tnx for topic dax | 01:22 |
|---|---|---|
| === guiverc_d is now known as guiverc | ||
| === cpaelzer__ is now known as cpaelzer | ||
| lotuspsychje | Lowl3v3l: welcome | 11:28 |
| lotuspsychje | Lowl3v3l: we dont really reccomend upgrading to a daily | 11:28 |
| Lowl3v3l | I know. | 11:28 |
| lotuspsychje | Lowl3v3l: the reason is, if some bug occur, the devs will have hard work to seperate where it comes from | 11:28 |
| lotuspsychje | Lowl3v3l: if you want to help testing 19.10, we advice a clean daily | 11:29 |
| Lowl3v3l | Okay. But this still does not answer my question why do-release-upgrade is blocking | 11:29 |
| Lowl3v3l | because either I fundamentally do not understand something about my system or it has a bug | 11:30 |
| lotuspsychje | not sure, maybe they block upgrade -d in early stage? | 11:30 |
| lotuspsychje | Lowl3v3l: is your system up to date? | 11:31 |
| Lowl3v3l | according to apt dist-upgrade it is | 11:31 |
| lotuspsychje | !uptodate | 11:31 |
| ubottu | To ensure you have all the latest known patches and security updates for your ubuntu installation, please update with the following command: `sudo apt update && sudo apt upgrade`. See also !upgrades and !security; you may also need to run `apt full-upgrade`. | 11:31 |
| lotuspsychje | Lowl3v3l: also, in this early stage, 19.10 doesnt differ much from 19.04 yet, maybe that could also be a reason, why you cant upgrade yet | 11:32 |
| Lowl3v3l | ubottu: already did so. | 11:32 |
| ubottu | Lowl3v3l: I am only a bot, please don't think I'm intelligent :) | 11:32 |
| lotuspsychje | its like you would upgrade to the same version | 11:33 |
| lotuspsychje | same kernel too probably atm | 11:34 |
| lotuspsychje | we have some bug testers running 19.10 already | 11:35 |
| lotuspsychje | i know one of the crew changed his sources to the 19.10 ones | 11:35 |
| lotuspsychje | just keep in mind, clean daily is the normal way to go | 11:36 |
| Lowl3v3l | I know. I am doing this more for shits and giggles. But even if all packages were the same, do-release-upgrade should be able to set the sources.list accordingly et cetera | 11:47 |
| Lowl3v3l | But thanks for your help anyway | 11:49 |
| lotuspsychje | np Lowl3v3l | 11:50 |
| lotuspsychje | the member changed sources just joined | 11:50 |
| lotuspsychje | wanna talk to him Lowl3v3l ? | 11:50 |
| Lowl3v3l | if he has time, sure :) | 11:51 |
| lotuspsychje | Lowl3v3l: talk to BluesKaj :p | 11:52 |
| BluesKaj | Lowl3v3l, I edited my /etc/apt/sources.list with sed command like so: sudo sed -i 's/disco/eoan/' /etc/apt/sources.list , then update and upgrade. Make sure your 19.04 packages are updated and upgraded first tho | 11:55 |
| Lowl3v3l | Hey BluesKaj, I was told you might have some insight on a little problem of mine. I just tried upgrading my 19.04(which has no third party repos or ppas and is fully updated itself) to development using do-release-upgrade -d. I am aware that a clean install is the better way, but do-release-upgrade -d tells me to upgrade my packages even though apt dist-upgrade is unable to find any outdated ones. Any idea on why it is behaving that wa | 11:56 |
| Lowl3v3l | y? I am aware of the manual way to update, but my problem really centers around this behaviour that i just dont understand | 11:56 |
| BluesKaj | Lowl3v3l, I don't understand your concern about "unable to find any outdated packages", that shouldn't be included in any upgrade | 11:59 |
| BluesKaj | if you have ppas, remove them just for safety's sake | 12:00 |
| Lowl3v3l | BluesKaj: my concern is that do-release-upgrade does not work because it tells me to update my packages even though according to apt all my packages are on the latest version | 12:00 |
| lotuspsychje | Lowl3v3l: can you pastebin the output please | 12:01 |
| BluesKaj | do-release-upgrade -d probly isn't working because the archive isn't ready yet | 12:02 |
| Lowl3v3l | BluesKaj: okay so lotuspsychje was right after all and I am not stupid :) thank you | 12:02 |
| lotuspsychje | yeah told Lowl3v3l its still in early stage atm | 12:03 |
| albert23 | sudo DEBUG_UPDATE_MANAGER=yes do-release-upgrade -d shows it reads https://changelogs.ubuntu.com/meta-release-development which doesn't list 19.10 yet | 12:03 |
| lotuspsychje | tnx albert23 | 12:04 |
| BluesKaj | Lowl3v3l, i ran it as well and there was nothing availabe | 12:04 |
| BluesKaj | the dailies are out for clean installers, but it's still early days for the archives | 12:05 |
| lotuspsychje | BluesKaj: that was on kubuntu right? | 12:05 |
| BluesKaj | yes | 12:05 |
| lotuspsychje | maybe they are faster? | 12:05 |
| BluesKaj | not sure | 12:06 |
| lotuspsychje | or would it be the same as albert23 says | 12:06 |
| lotuspsychje | not added yet | 12:06 |
| BluesKaj | yeah, too early | 12:06 |
| lotuspsychje | looks like you will have to marry a daily Lowl3v3l :p | 12:07 |
| BluesKaj | it usually takes a couple of weeks for the repos/archives iiirc | 12:07 |
| lotuspsychje | yeah but this time dailys showed up real quick | 12:08 |
| BluesKaj | for clean installers | 12:08 |
| lotuspsychje | yes | 12:08 |
| BluesKaj | one can edit the sources.list tho and that will work, as i mentioned above | 12:10 |
| BluesKaj | Lowl3v3l,, you may have to switch your server in muon to the "main server" which is in the UK | 12:11 |
| BluesKaj | or synaptic, which ever package manager you use | 12:12 |
| Lowl3v3l | the german server seems to have the packages already. | 12:13 |
| BluesKaj | ok good | 12:13 |
| === luxifer_ is now known as luxifer | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!