Hi,
On 12-04-2025 10:58, Bastian Blank wrote:
On Sat, Apr 12, 2025 at 09:56:02AM +0200, Paul Gevers wrote:
What we can already do is ask packages that depend on Essential packages, to
add a hint-testsuite-triggers [1] test. That way we would at least know
which packages to test for.
People al
On Sat, Apr 12, 2025 at 09:56:02AM +0200, Paul Gevers wrote:
> We *could* trigger all tests for each essential package. Given how much help
> glibc typically already needs due to flaky tests, I don't think we should do
> that already. We'd also run into infrastructure limitations.
>
> What we can
Am 12.04.25 um 09:56 schrieb Paul Gevers:
Hi,
On 12-04-2025 08:34, Marc Haber wrote:
Otoh, Essential packages can break many other packages without having
an explicit reverse dependency listed since they are assumed always
present and since it's a bug to explicitly list a dependency on an
Ess
Hi,
On 12-04-2025 08:34, Marc Haber wrote:
Otoh, Essential packages can break many other packages without having an
explicit reverse dependency listed since they are assumed always present
and since it's a bug to explicitly list a dependency on an Essential
package.
Conform 3.5: "Packages a
Hi,
non-essential packages stay stuck in unstable when autopkgtests of one
of their reverse dependencies fails their autopkgtests¹. This is
generally a good thing.
Otoh, Essential packages can break many other packages without having an
explicit reverse dependency listed since they are assum
5 matches
Mail list logo
