| keithzg[m] | Is there a filter or wiki page or anything out there listing what's holding up the 20.04 LTS prompts? Not that I don't trust that it's being held up for good reason, I'm just curious :) | 01:02 |
|---|---|---|
| keithzg[m] | (I had previously had the impression that systems set to "Prompt=lts" would get the prompt when the .1 of the release was minted, but either that was always purely correlative rather than causative or something's different this release?) | 01:08 |
| sarnold | indeed I think it was always coincidental | 01:09 |
| sarnold | I did see a suggestion once of which specific bug was holding things up, but I've forgotten no wwhich one it is | 01:09 |
| keithzg[m] | Hmm so it's just someone at Canonical decides when to flip the switch? Or at very least the criteria is not public? Not a wholly unreasonable way to do things, I guess I just always assumed there was some more formal process for thresholds, ex. no confirmed critical bugs tagged against the release (and I do see one such bug at https://bugs.launchpad.net/ubuntu/+bugs?field.tag=focal&orderby=-importance so is that | 01:19 |
| keithzg[m] | it?). | 01:19 |
| keithzg[m] | So far have had no problems upgrading any of my systems from 18.04 to 20.04 other than the one that was using Icinga2's own repos, and they broke configs in a point release, so that was definitely not a problem on the Ubuntu side of things, hah! | 01:20 |
| keithzg[m] | But, not knowing exactly why the rollout is currently delayed I've mostly been cautious, certainly with the systems I admin for work; at home I'm a bit more cavalier ;) | 01:21 |
| rfm | The release status page that tracks the upgrade-stopper bugs is https://discourse.ubuntu.com/t/focal-fossa-20-04-1-lts-point-release-status-tracking/17604 | 01:27 |
| sarnold | oh nice, that's better than what I was about to suggest | 01:27 |
| sarnold | (I was going to suggest scraping all the ubuntu-release channel logs from https://irclogs.ubuntu.com/2020/ and looking for mentions of 20.04.1 :) | 01:28 |
| rfm | The fix for the last stopper bug has been released to focal-updates (it came down yesterday for me) so it shouldn't be too much longer | 01:29 |
| cliluw | Is there a site that lets me view info documents online? I know so many sites to read man pages online, but none to read info docs. | 01:42 |
| sarnold | cliluw: the pinfo tool can make reading info files locally a little less horrible | 01:47 |
| sarnold | I thought debian systems had a 'winfo' or similar that would reexport them to a web interface of some sort but I'm not spotting it now.. | 01:47 |
| sarnold | cliluw: if it is debian-packaged you can read the info files via their sources.debian.org service, eg https://sources.debian.org/data/main/g/grub2/2.04-9/docs/grub.info#L36 | 01:48 |
| sarnold | but that means you have to find the thing in the source. it's a bit of a pain in the butt but I use this for reading manpages all the time. | 01:49 |
| cliluw | sarnold: That sounds even harder than using the "info" command. :-P | 01:50 |
| cliluw | Thanks for the suggestions though. | 01:50 |
| sarnold | I read manpages for *loads* of things that I don't want to install just to read the page :) | 01:52 |
| === Seveas_ is now known as Seveas | ||
| === vlm_ is now known as vlm | ||
| === vlm_ is now known as vlm | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!