| webchat95 | I joined earlier but my internet didn't help. Now I'm able to ask: is editing /etc/apt/sources.list and replacing focal with jammy the "proper" way to get the daily jammy? | 00:58 |
|---|---|---|
| tomreyn | installing from an iso image would be, i guess | 01:04 |
| webchat95 | I want to upgrade the existing install, so waiting for a ISO wouldn't work. I'm doing the upgrade now | 01:27 |
| webchat95 | 2 packages will be kept on its current versions, 395 new packages, 3500 packages to update, 37 packages to remove, 5444 MB to download, 2277 MB extra space used | 01:28 |
| webchat95 | This install survived the same process from Bionic to Focal, so I'm hopeful it will at least boot | 01:29 |
| webchat95 | It's a bit unfortunate how apt can download only one package per repository at once, the so many 20 kB packages slow down the entire process. Of course, a huge update like this is a relatively uncommon event | 01:36 |
| Bashing-om | webchat95: LTS to LTS is supported. from focal to jammy however, there are 20.10 and 21.04 and 21.10 in between to upgrade too :( | 01:38 |
| tomreyn | this sounds like you're upgrading a system you want to work reliably to an early development state of the next ubuntu release. unless you have much experience, that can be a bad choice | 01:38 |
| tomreyn | webchat95: ^ | 01:38 |
| webchat95 | tomreyn : I'm trusting it won't be much worse than the bionic to focal experience. I'm upgrading a relevant system because back then it allowed me to find bugs I wouldn't be able to find testing on clean install | 01:47 |
| webchat95 | This time I have a real full disk backup. It's a truly a bad idea to do it without backups | 01:48 |
| tomreyn | webchat95: oh so if your goal is to contribute to testing (and report bugs, and maybe do some debugging), then that's a good way to contribute for sure. | 01:49 |
| Bashing-om | webchat95: But ! bionic to focal is LTS-LTS - running thrrough the "testing" releases is a bit different in that you are required for compatibility to upgrade to each in the path :( | 01:49 |
| webchat95 | I did the bionic-focal like in october/2019, so around the same moment (~6 months before) | 01:50 |
| tomreyn | so also without an existing migration path (other than dist-ugrade). that may explain a bumpy ride. | 01:51 |
| Bashing-om | !upgrade | webchat95 Hope here to prevent some heartaches | 01:54 |
| ubottu | webchat95 Hope here to prevent some heartaches: For upgrading, see the instructions at https://help.ubuntu.com/community/UpgradeNotes - see also http://www.ubuntu.com/desktop/get-ubuntu/upgrade | 01:54 |
| webchat95 | Update: the download finished, it's installing now 🤞️ | 02:18 |
| alkisg | webchat95: tell us of your results; I'm tempted to do the same next week :) | 03:20 |
| webchat95 | alkisg libnma-common and network-manager-gnome packages try to write the same file, breaking the update. Many -dev packages have conflicts. The second attempt of finishing the install is running, roughly 1300 packages were unpacked, so far | 03:34 |
| webchat95 | Other than some icons missing, it seems to be OK, but I'll wait and see to confirm | 03:35 |
| webchat95 | One thing I noticed is that the dialog to replace a configuration file can be different: sometimes it opens a type of window, sometimes it's another type of window, sometimes it's in a terminal. It's always the same keep/replace/show diff options, but there is some inconsistency regarding the interface used | 04:04 |
| webchat95 | The installation process finished. Something triggered a postfix install 🤦♂️️ and 4 packages failed: openjdk-8-jre-headless:amd64 openjdk-8-jre:amd64 openjdk-8-jdk-headless:amd64 openjdk-8-jdk:amd64 | 04:24 |
| Bashing-om | !info openjdk-8 impish | 04:26 |
| ubottu | Package openjdk-8 does not exist in impish | 04:26 |
| Bashing-om | !info openjdk-9 impish | 04:27 |
| ubottu | Package openjdk-9 does not exist in impish | 04:27 |
| webchat95 | Makes sense, the version 11 is installed | 04:27 |
| Bashing-om | !info openjdk-8 focal | 04:27 |
| ubottu | Package openjdk-8 does not exist in focal | 04:27 |
| webchat95 | I'll reboot now. If everything goes right, I should be back in less than 10 minutes (5400 RPM HDD speeds) | 04:28 |
| webchat95 | It worked, I'm on Ubuntu Jammy Jellyfish (development branch) x86_64 | 04:34 |
| webchat95 | More precisely, Xubuntu. I really liked the default background | 04:34 |
| webchat95 | The volume icon disappeared from the panel 🤔️ | 04:37 |
| alkisg | Sounds good! I'll upgrade my MATE later on | 04:42 |
| webchat95 | The installation failed twice, be sure you will be able to fix the breakages, especially if it's NetworkManager and you have no internet | 04:43 |
| alkisg | Will do, thank you! | 04:58 |
| lotuspsychje | a page has been created, iso has yet to come http://iso.qa.ubuntu.com/qatracker/milestones/429/builds | 09:12 |
| === pikapika is now known as pikapi | ||
| === pikapi is now known as pikapika | ||
| ooshlablu | hello, I'm reaching out here because I've created a few docker containers for various games and have created scripts that can build packages for them for various versions of ubuntu | 14:26 |
| ooshlablu | https://github.com/ooshlablu/dolphin-docker | 14:26 |
| ooshlablu | https://github.com/ooshlablu/performous-docker | 14:26 |
| ooshlablu | I have also done so for stepmania and pcsx2, will be pushing those up shortly | 14:27 |
| ooshlablu | is there anyone I can talk to about getting these packages into the 22.04 cycle? | 14:27 |
| ooshlablu | on a side note, performous will be releasing version 1.2 shortly | 14:27 |
| === genii-core is now known as genii | ||
| === Mekaneck is now known as Fatal_Sushi | ||
| lotuspsychje | [telegram] <Leokolb> Budgie Jammy 22.04 iso's now available for testing | 18:39 |
| lotuspsychje | [telegram] <Leokolb> Lubuntu Jammy also available 😊 | 18:39 |
| alkisg | Leokolb, links? | 18:52 |
| Fatal_Sushi | alkisg: http://iso.qa.ubuntu.com/qatracker/milestones/429/builds | 19:03 |
| alkisg | Thanks! | 19:03 |
| Fatal_Sushi | yw | 19:03 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!