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

[Heinrich Schuchardt]

On 5/3/24 08:23, Michael Hudson-Doyle wrote:
> 
> 
> On Fri, 3 May 2024 at 03:05, Heinrich Schuchardt 
> <heinrich.schuchardt at canonical.com 
> <mailto:heinrich.schuchardt at canonical.com>> wrote:
> 
>     On 02.05.24 16:46, Robie Basak wrote:
>      > On Thu, May 02, 2024 at 04:05:31PM +0200, Heinrich Schuchardt wrote:
>      >> Often I see apt-get update downloads exceeding 100 MiB. That is
>     without a
>      >> single package download.
>      >
>      > I think it might be worth quantifying this. Right now, for amd64
>      > proposed pocket Packages.xz files for the following:
> 
>     This is what I see:
<snip />>     Translation-en [118 kB]
>     Fetched 147 MB in 10s (14,3 MB/s)
> 
> 
>     Reading package lists... Done
> 
> 
> Yes sure but that's not the common experience for at least three reasons:
> 
>   1. it's the devel series so the release pocket gets republished all 
> the time
>   2. you have apt-file installed and are downloading the Contents files. 
> those are always big
>   3. you have deb-src enabled (this makes much less difference than the 
> previous 2 though)
> 
> If we want to make apt update quicker / lighter on resources we should 
> figure out if we can stop publishing some of the hashes (which entirely 
> dominate the size of the compressed package lists). We currently have 4 
> hashes in the lists (md5, sha1, sha256, sha512) -- I know Dimitri was 
> trying to get us to the point that we could stop publishing MD5 at least 
> but there are a few things out there that hardcode a dependence on it. 
> Maybe oracular is a good time to turn off some hashes and see what breaks.
> 

With unattended upgrades or cron-apt the meta information is downloaded 
at least daily. Most of the downloaded data doesn't change.

On Debian I have seen apt-update downloading diff files. Why don't we 
use those for Ubuntu especially for the large files like Contents?

Best regards

Heinrich