Re: request to remove "-updates" repository
On Sun, 2020-04-05 at 19:03 +0100, Samuel Henrique wrote:
> I know I'm risking being unaware of something that invalidates this
> request, so please also consider this a request for clarifications if
> it's the case.
>
> While discussing #954460 [0] with Cyril, I decided to give it a try
> to update the debian-reference section which mentions the "-updates"
> repository[1], to make it more informative on what it's about, and
> noticed that the reference does not mention that this repository is
> enabled by default, currently putting it side-by-side with the
> backports repository (which I consider a bad thing).
By -updates, I assume you mean stable-updates.
> So I started thinking about how the whole section should be rewritten
> to make it more clear how Debian deals with point releases and stable
> updates, and I realized that "-updates" could actually just be
> removed totally and updates could be pushed to the main repository
> instead, thus reducing the complexity and helping with the user
> confusion about what is "-updates" and how point releases works[2].
What do you mean by "the main repository" here?
The entire point of stable-updates is that it contains packages that
will be in a point release (and thus are already in proposed-updates)
but that for some reason have been identified as important enough to be
offered to users before the point release occurs.
How would you see that function being fulfilled if the stable-updates
suites were removed?
> [2] unfortunately it's still very common for users to not understand
> point releases are just the transition from -updates to the main
> repo, and that considering -updates is already enabled, it makes no
> difference as long as the system is updated.
Point releases move packages from proposed-updates to stable, not from
stable-updates. Packages in stable-updates never move to any other
suite.
Regards,
Adam
Reply to: