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. -- Colin Watson (he/him) [cjwat...@ubuntu.com] -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel