Hi,
On 09-04-2024 6:23 p.m., Paride Legovini wrote:
* runner/autopkgtest talks to the backend with a simple text
protocol. While this enables users to add another backend without
changes to the src:autopkgtest code trivially, the drawback of that
is loosing all nuance of what really is going on
Hi,
On 09-04-2024 6:23 p.m., Paride Legovini wrote:
PS: would it be worth it to enable dashboards for autopkgtest on
salsa to manage this project? I assume issues on salsa are disabled
on purpose to avoid bug reports in multiple places. Could we make
adding issues project members only?
I'm in
Hi Paul,
On 2024-04-07 16:42, Paul Gevers wrote:
> The following issues have come up several times over the years. I
> propose to discuss them in one place (this bug report) to define the
> solution strategy. I haven't gone through all the details myself, so
> I might be thinking in the wrong
Hi,
On 07-04-2024 7:20 p.m., Christian Kastner wrote:
I'm not a maintainer but I use autopkgtest a lot. I hope it's OK if I
contribute input.
Yes, absolutely. Comments from all people that want to contribute
constructively are welcome. Even more so from users and contributors.
Paul
Hi Paul,
On 2024-04-07 16:42, Paul Gevers wrote:
> The following issues have come up several times over the years. I
> propose to discuss them in one place (this bug report) to define the
> solution strategy. I haven't gone through all the details myself, so I
> might be thinking in the wrong
Package: autopkgtest
Severity: wishlist
Hi all,
The following issues have come up several times over the years. I
propose to discuss them in one place (this bug report) to define the
solution strategy. I haven't gone through all the details myself, so I
might be thinking in the wrong
6 matches
Mail list logo
