Make proposed available by default? [was: Setting NotAutomatic for hirsute+1-proposed]

Heinrich Schuchardt heinrich.schuchardt at canonical.com
Thu May 2 14:05:31 UTC 2024


On 02.05.24 15:30, Robie Basak wrote:
> On Thu, Jan 21, 2021 at 02:15:59AM -0800, Julian Andres Klode wrote:
>> I'd like to suggest that we start setting NotAutomatic: yes for the
>> proposed pocket with hirsute+1, such that things like SRU verification
>> will be easier, and all those people who enable proposed in sources.list
>> for I don't know what reasons don't get their systems destroyed as much.
> 
> Now that we have an LTS out with NotAutomatic: yes, I wonder if it would
> be worth looking to add the proposed pocket in apt sources by default
> everywhere in future releases, like we do for backports[1].
> 
> Upside: it would make for even simpler instructions for users to test
> something from proposed.
> 
> Downside: users would have yet more downloading on "apt update",
> although perhaps we should expect the proposed lists to be small?

Often I see apt-get update downloads exceeding 100 MiB. That is without 
a single package download.

When working with a mobile connection this is already problematic. We 
should strive to get this number down. Adding proposed is going into the 
wrong direction and would only help a tiny fraction of all users.

Best regards

Heinrich

> 
> To be clear, I'm on the fence, and polling for opinions.
> 
> Robie
> 
> [1] There are so many ways of deploying Ubuntu now that perhaps it's
> worth reviewing them for consistent behaviour.
> 
> 




More information about the ubuntu-devel mailing list