On Mon, Dec 13, 2021 at 9:04 AM Colin Watson <cjwat...@ubuntu.com> wrote: > > On Mon, Dec 13, 2021 at 08:32:53AM -0500, Dan Streetman wrote: > > Just to clarify, people won't need to manually specify all > > dependencies, right? For example, if testing the 'systemd' package > > from -proposed, simply doing 'apt install systemd/jammy-proposed' > > would install the proposed version of systemd *and also* the proposed > > version of libsystemd0? > > That's how it behaves in my tests, yes - if a dependency imposes a > version constraint requiring a lower-priority version, then apt tries to > satisfy it. > > > Also, is this really needed? Is it really so hard for people to just do: > > > > $ sudo add-apt-repository -p proposed > > > > ...install proposed package(s) normally and do tests... > > > > $ sudo add-apt-repository -r -p proposed > > This has been an issue on and off for at least a decade, so my > impression is that we have solid empirical evidence that this is indeed > too hard for many testers in practice.
Ok, but the (non-graphical) method of enabling/disabling the proposed pocket is quite painful on focal and earlier, so maybe now that users can simply use add-apt-repository to enable/disable it with a 1-line command, it might not be as much of an issue? Updating the 'EnableProposed' wiki page might help, since currently it seems hugely over-complicated and out of date. Anyway, if the change is made so apt treats the proposed pocket the same as the backports pocket, i assume (hope) all new systems will have the proposed pocket enabled by default in their sources.list? > > -- > Colin Watson (he/him) [cjwat...@ubuntu.com] > > -- > technical-board mailing list > technical-board@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/technical-board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
