Pre-released updates ON by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When installing a fresh Ubuntu 20.04 from an USB Stick, then in the "Software & Updates" settings window, where there is a possibility to set up software sources, on the "Developer Options" tab the "Pre-released updates (focal-proposed)" checkbox is ON by default, therefore installing pre-release packages for regular users as well.
And not just when booting from the installation media (USB stick), but after installing the system onto the main HDD / SSD , the situation is the same.
The issue popped up when I already had gnome-shell 3.36.2 on my system (completely killing gnome-tweaks), while the latest stable release was just 3.36.1
Thanks to #ubuntu IRC channel and especially "ioria" user to help me figuring out what is going on.
The installation ISO image I was used has the signature from 3rd May.
$cat /var/log/
Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200503)
$lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04
$uname -a
Linux sarmx777 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSign
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Mon May 18 20:06:44 2020
InstallCmdLine: file=/cdrom/
InstallationDate: Installed on 2020-05-11 (7 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200503)
SourcePackage: ubiquity
Symptom: installer
UpgradeStatus: No upgrade log present (probably fresh install)
affects: | ubuntu → ubiquity (Ubuntu) |
https:/ /wiki.ubuntu. com/PointReleas eProcess suggests that building images with -proposed enabled is a deliberate action for LTS point releases unless building images less than a week before the actual point release (if I've read everything correctly - the last eight lines are important).
So not a bug although I'm still unclear why the decision to enable -proposed has been made unless it's simply to install updates that are intentionally not promoted from -proposed until the point release is made final, e.g. HWE stack.